[Amportal-devel] Re: Amportal-devel digest, Vol 1 #507 - 16

On Tuesday 02 May 2006 08:19, Philippe Lindheimer wrote:

[quote] SUGGESTION TO EVERYONE:

When we commit and it addresses something in a specific bug (or set of
bugs), let’s put the bug number(s) in the commit message as well as putting
the Rev number (Change Set number) in the ticket(s) that we close.
[/quote]
FYI: Trac will turn revision numbers and ticket numbers into links if
formatted like:

r1734
#701

Ryan


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


Amportal-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-devel

Post generated using Mail2Forum (http://www.mail2forum.com)

[quote=“Bentley”]On Tuesday 02 May 2006 08:19, Philippe Lindheimer wrote:

[quote] SUGGESTION TO EVERYONE:

When we commit and it addresses something in a specific bug (or set of
bugs), let’s put the bug number(s) in the commit message as well as putting
the Rev number (Change Set number) in the ticket(s) that we close.
[/quote]
FYI: Trac will turn revision numbers and ticket numbers into links if
formatted like:

r1734
#701

Ryan
[/quote]

One other think I should mention is that the revision numbers in Trac are always 1 ahead of the actual revision number. I’m not sure there is a way around this.

I use SVK to mirror the sf.net svn repo locally:

http://svk.elixus.org/

When SVK pulls changes, it does something like:

[code:1]

svk sync //amportal

Syncing https://svn.sourceforge.net/svnroot/amportal
Retrieving log information from 1815 to 1815
Committed revision 1816 from revision 1815.
[/code:1]

… so r1815 in sf.net svn is saved as r1816 locally. Very frustrating. I went on #svk irc today in search of a solution. The only response was “there’s no easy solution”. [sigh].

Ryan