[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Git transition checklist

From: Rüdiger Sonderfeld
Subject: Re: Git transition checklist
Date: Thu, 09 Jan 2014 17:45:28 +0100
User-agent: KMail/4.11.3 (Linux/3.11.0-14-generic; KDE/4.11.3; x86_64; ; )

On Thursday 09 January 2014 18:17:52 Eli Zaretskii wrote:
> > From: Andreas Schwab <address@hidden>
> > Cc: Rüdiger Sonderfeld <address@hidden>,
> > 
> >   address@hidden,  address@hidden
> > 
> > Date: Thu, 09 Jan 2014 12:10:27 +0100
> > 
> > Eli Zaretskii <address@hidden> writes:
> > > If you suggest doing the above by hand, then that won't do the job:
> > > people will forget and/or use different formats for the text.  We need
> > > something better, if it's possible.
> > 
> > Notes can be added, removed and modified independently from the commits
> > they are attached to, so anybody can fix it up.
> Yes, but only after the problem is discovered and/or reported.  Until
> then, it could lay dormant for a long time.  Again, this happened in
> the past.

What does --fixes in bzr exactly do?  Does it close the corresponding bug on 
the tracker?  Does that happen when you commit or when you push?

This could be handled automatically in a pre-receive hook.  It depends on what 
exactly we need to do.  Is it enough to check the format?  That would be 
simple.  Checking if it matches an existing bug and closing the bug would be a 
bit more complicated because it requires interaction with the bug tracker.

But I'm currently more concerned with the fact that notes aren't automatically 
pushed.  So maybe git-notes aren't useful in our case.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]