[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <7008541.g5m1pJPVp1@vostro.rjw.lan>
Date: Mon, 29 Jul 2013 15:10:33 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Jiri Kosina <jkosina@...e.cz>, Samuel Ortiz <sameo@...ux.intel.com>
Cc: ksummit-2013-discuss@...ts.linuxfoundation.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists