lkml.org 
[lkml]   [2010]   [Apr]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/3] Documentation: -stable rules: upstream commit ID requirement reworded
On Sat, Apr 24, 2010 at 11:30:16AM +0200, Stefan Richter wrote:
> Stefan Richter wrote:
> > tytso@mit.edu wrote:
> >> I find the upstream commit ID to be highly useful when looking at
> >> commits in the stable tree. So it would be nice IMHO if we could
> >> enforce this requirement regardless of whether the submission path is
> >> via e-mail or git.
> ...
> > Apparently Greg's scripts modify the
> > changelogs respectively when he cherry-picks from linux-2.6.git, so the
> > requirement is also always fulfilled with this alternative submission path.
>
> Or do you mean submission directly from a developer's git tree to stable
> via git pull by Greg? Is this been done? If yes, I suppose this comes
> only from people who know very well how a stable patch is meant to look
> like. Nevertheless I could send another adjustment for
> Documentation/stable_kernel_rules.txt if this is another actual
> submission path.

No, it's not a real submission patch, and yes, I always require a git
commit id in the patch. If I don't have it, it is explained in the
patch why it is not in Linus's tree.

Don't worry, I think the current wording is fine.

thanks,

greg k-h


\
 
 \ /
  Last update: 2010-04-24 17:19    [from the cache]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and my Meterkast|Read the blog