PATCH: Add FIXED-IN keyword support to commit messages.
mpyne at kde.org
Tue May 18 23:08:47 BST 2010
On Tuesday, May 18, 2010 13:10:54 David Faure wrote:
> On Friday 07 May 2010, Michael Pyne wrote:
> > On Thursday, May 06, 2010 07:49:31 Oswald Buddenhagen wrote:
> > > On Thu, May 06, 2010 at 12:00:17PM +0200, David Faure wrote:
> > > > On Thursday 06 May 2010, Olivier Goffart wrote:
> > > > > Would it be possible to guess that automatically from the branch
> > > > > the fix is pushed in?
> > > >
> > > > No, since a commit in the stable branch the last week before the
> > > > release, could or could not go into the actual release. Only a human
> > > > can know if the commit will make it into the upcoming release or not.
> > >
> > > the version table would use the initial branching/tagging point. this
> > > would err on the pessimistic side, which is perfectly fine. if the
> > > release dude cares, he may still fix the field after he
> > > cherry-picks/retags.
> > Well I gave it a shot based on the idea that most of the things we care
> > about auto-detecting in branch will be in /branches/KDE/$branch/module.
> > I've also fixed the field name for the email.
> > Can someone with karma please look this over and if it works, commit?
> > Feel free to extract the auto version detection if it doesn't work.
> Committed, but didn't work, see https://bugs.kde.org/show_bug.cgi?id=140970
Hmm, I think it would be instructive to see if the email was generated
properly and Bugzilla messed it up, or if the email was not generated
properly. I'll see if I can play around with feeding an example commit log
into the script and see what I get I guess.
- Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel