On Wed, Feb 18, 2009 at 12:55 AM, Steve Borho <st...@borho.org> wrote: > On Wed, 2009-02-18 at 00:06 +0000, TK Soh wrote: >> On Tue, Feb 17, 2009 at 5:46 PM, Steve Borho <st...@borho.org> wrote: >> > Hello, >> > >> > It had been my intention to keep separate issue tracking instances for >> > -stable and -crew, but I've changed my mind and decided to use a >> > single issue tracking instance on -stable that convers both >> > repositories. There were two primary reasons for this: >> > >> > 1) I wasn't looking forward to moving issues at release time >> > 2) Bitbucket now supports issue commands in commit messages, so issues >> > in the -stable tracker will automatically get updated when we push >> > properly annotated changes to the -stable repository. >> > >> > The issue commands would not work correctly if crew had it's own issue >> > tracker, so I've disable the crew tracker (it had no issues in it >> > yet). >> > >> > I've updated the contributing guidelines on the wiki to describe how >> > this works. Essentially, if your patch fixes issue #1 in the -stable >> > issue tracker, you should include 'fixes #1' in the commit message. When
Just to be sure, can you give an example of the commit message? >> Is this "#1" a syntax required by BB to in order for some systems to >> work? Else, I would recommend something like "BB#1" to distinctively >> differentiate them from SF trackers. > > Their script accepts: > fixes issue 1 > fixes #1 > fixes 1 > > I'm not too worried anyone is going to confuse our bb issue numbers with > the seven digit ones from sourceforge. If you're concerned about side > effects, use '[ 0000000 ]' syntax when referring to the SF bug reports. I think SF bugs should continue to show in "SF bug #123456" format, since it already doesn't tie to BB tracker. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
