mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jiri Kosina <jkosina@suse.cz>, Samuel Ortiz <sameo@linux.intel.com>
Cc: ksummit-2013-discuss@lists.linuxfoundation.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process
Date: Mon, 29 Jul 2013 15:10:33 +0200	[thread overview]
Message-ID: <7008541.g5m1pJPVp1@vostro.rjw.lan> (raw)
In-Reply-To: <alpine.LNX.2.00.1307291230270.18809@pobox.suse.cz>

On Monday, July 29, 2013 12:31:37 PM Jiri Kosina wrote:
> On Mon, 29 Jul 2013, Samuel Ortiz wrote:
> 
> > - Developement process: Jon Corbet's article about our changelog raised
> >   one interesting question: How can we better track how single SOB
> >   patches are getting merged ?

That actually is simple enough.

Check out the Linus' master branch and do

$ git log --ancestry-path --merges <commit>..

and read the log from the bottom to the top.

> >   Should maintainers add their SOB when
> >   they pull from subsystems maintainers (If they can) ? This is
> >   something I care about from both my MFD and NFC maintainer
> >   perspectives as I both pull from MFD sub maintainers and am John
> >   Linville's NFC sub maintainer.
> 
> This is difficult ... I think that in some sense merging from subsystem 
> maintainer tree can be viewed as an "implicit" Signoff, although this 
> hasn't been formalized anywhere.
> 
> I am afraid there is no way git could handle this easily without rebasing.

No, there's none, as you'll always change the commit hash by adding tags to it.

Thanks,
Rafael


       reply	other threads:[~2013-07-29 13:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130729102452.GA2682@zurbaran>
     [not found] ` <alpine.LNX.2.00.1307291230270.18809@pobox.suse.cz>
2013-07-29 13:10   ` Rafael J. Wysocki [this message]
2013-07-29 14:11     ` Jonathan Corbet
2013-07-29 16:31       ` Paul Gortmaker
2013-07-29 16:33         ` Jiri Kosina
2013-07-29 22:09       ` Rafael J. Wysocki
2013-08-01 10:16         ` Geert Uytterhoeven
2013-08-01 17:40           ` Rafael J. Wysocki
     [not found] ` <20130729113526.GB3604@zurbaran>
     [not found]   ` <20130729130357.GQ29916@titan.lakedaemon.net>
2013-07-29 13:27     ` Rafael J. Wysocki
2013-07-29 18:17       ` John W. Linville
2013-07-29 18:41         ` Jason Cooper
2013-07-29 22:30         ` Rafael J. Wysocki
2013-07-31  5:47           ` H. Peter Anvin
2013-07-31  5:56             ` James Bottomley
2013-07-31 11:48             ` Rafael J. Wysocki

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=7008541.g5m1pJPVp1@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=jkosina@suse.cz \
    --cc=ksummit-2013-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /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

all inboxes | Powered by JetHome®