[Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

Takashi Iwai tiwai at suse.de
Mon Jul 29 16:34:07 UTC 2013


At Mon, 29 Jul 2013 18:12:34 +0200 (CEST),
Jiri Kosina wrote:
> 
> On Mon, 29 Jul 2013, Greg KH wrote:
> 
> > > In some other thread here I was proposing to change stable workflow so 
> > > that maintainers will be sending pull requests of stable branches to Greg, 
> > > which would IMHO have several benefits, including this.
> > 
> > Not really, as I would then turn that git pull request into a quilt
> > series of patches, loosing that information :(
> 
> I understand that, but if the maintainers were the ones preparing the 
> branch to be pulled, the assumption is that there will be much less 
> patches dropped, so quilt will be unnecessary.
> 
> What is so special about -stable that the same model Linus is using can't 
> be applied in case responsible sub-maintainers prepare branches for you to 
> pull?

In the case of stable kernels, there is a review phase, where the
patches aren't committed to the git tree yet.  It happens often that
inappropriate patches are dropped during it.  If the processing is
changed to use a git pull, we'll have to add a revert commit instead
of dropping a patch, which is messy as a stable tree.  This is a
disadvantage of git pull, at least.


Takashi


More information about the Ksummit-2013-discuss mailing list