Dear Phil, by the way, the "svn copy" commits, could you please include the revision number you are copying from? In SVN, it isn't easy to see from the outside which revision of trunk was tagged as 2.3.5. The (new) revision of the tag itself (here: 18284) doesn't say anything about the revision of trunk where you copied from. Hence, I propose you write a log message as follows: "(re)tagged version 2.3.5, copied from trunk r11111". This makes it much easier to see already from the log messages that the original tag was from, say, trunk r18200, whereas the new tag is trunk r18210.
Thanks! Christian Am Samstag, 29. August 2009 02:37 schrieb Phil Longstaff: > Author: plongstaff > Date: 2009-08-28 20:37:31 -0400 (Fri, 28 Aug 2009) > New Revision: 18284 > Trac: http://svn.gnucash.org/trac/changeset/18284 > > Added: > gnucash/tags/2.3.5/ > Log: > Retag 2.3.5 > > > _______________________________________________ > gnucash-patches mailing list > gnucash-patc...@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-patches _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
