ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.com>
To: Greg KH <greg@kroah.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] services needed from kernel.org infrastructure
Date: Wed, 8 Jul 2015 17:08:50 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1507081704380.10183@pobox.suse.cz> (raw)
In-Reply-To: <20150708145910.GA11945@kroah.com>

On Wed, 8 Jul 2015, Greg KH wrote:

> > For example, please correct me if I am wrong, but I believe that if I send 
> > you a patch that would have authorship
> > 
> > 	Jiri Kosina <jkosina`rm -rf .`@suse.com>
> > 
> > and you wouldn't notice prior to applying it using the above do.sh, I 
> > think your precious tree is gone.
> 
> Note, I don't have "precious" trees, nor "precious" development systems,
> that's what git is for :)

Oh, sure, that was just an example because I was too lazy to construct a 
command that would send me your ssh keys :)

> > This would be caught immediately if it's properly maintained "project".
> 
> Hm, ok, but different maintainers have different needs.  James's git
> hooks are also really nice, and work for some workflows (note, I use
> them for some stable workflows).  Wolfram has published his scripts that
> he uses for applying and testing patches in the past as well, and while
> they were great for him, they didn't fit mine at the time.

Yes, my main point really was that I personally would find it super-nice 
to just mark particular branches in my kernel.org repositories as "send 
notifications for these", and author (and anyone else in "-by:" lines) 
would automatically receive nice notification once commit appears there. 
Without any need of wrapping simple git-am + git push with more and more 
bloated scripting.

Thanks,

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2015-07-08 15:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 20:42 Jiri Kosina
2015-07-07 22:40 ` Mark Brown
2015-07-07 22:52   ` Dmitry Torokhov
2015-07-08  2:16     ` Greg KH
2015-07-08  8:02       ` Jiri Kosina
2015-07-08  9:35         ` Mark Brown
2015-07-08 14:01           ` Theodore Ts'o
2015-07-08 14:36             ` Jason Cooper
2015-07-08 14:40             ` Jiri Kosina
2015-07-08 15:00             ` Greg KH
2015-07-12 12:55             ` Fengguang Wu
2015-07-13 16:22               ` Steven Rostedt
2015-07-14 13:07                 ` Fengguang Wu
2015-07-08 14:59         ` Greg KH
2015-07-08 15:08           ` Jiri Kosina [this message]
2015-07-08 15:42             ` Steven Rostedt
2015-07-07 22:53   ` josh
2015-07-08  7:35   ` Jiri Kosina
2015-07-08 13:05   ` Jason Cooper
2015-07-07 23:31 ` Andy Lutomirski
2015-07-07 23:37   ` Guenter Roeck
2015-07-07 23:38     ` Andy Lutomirski
2015-07-08  8:01   ` Geert Uytterhoeven
2015-07-08  7:31 ` James Bottomley
2015-07-08 13:25 ` Konstantin Ryabitsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.00.1507081704380.10183@pobox.suse.cz \
    --to=jkosina@suse.com \
    --cc=greg@kroah.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox