On Tue, Mar 23, 2004 at 04:04:19PM -0500, Francois Beausoleil wrote:
> Hello Brad !
> On Tue, 23 Mar 2004 14:40:19 -0600, "Brad Appleton" <firstname.lastname@example.org>
> > On Tue, Mar 23, 2004 at 02:10:24PM -0600, C. Michael Pilato wrote:
> > $ svn commit --message "Corrected # of cheese slices."
> > Sending sandwich.txt
> > Transmitting file data .
> > Committed revision 3
> > $ myrevmap -revnum 3 -revname MyRevName
> > Associated revision 3 of <??> with 'MyRevName'
> > $ svn log --revision `myrevnum MyRevName`
Note that there was some more text above that discussing other
possible alternatives (one of which was tagging).
> Why can't you just do:
> $ svn commit --message "Corrected # of cheese slices."
> Sending sandwich.txt
> Transmitting file data .
> Committed revision 3
> $ svn copy --message "Tagging release 4.0.1-b2" --revision 3
> Committed revision 4
Yes. That was the first alternative discussed (and the person
wanted a way for that to happen automatically). Speaking for
me personally, I wouldn't use a tag unless what I really wanted
was a tag that included a corresponding working-copy that would
show up in the svn pathspace. I would not do that for every
commit, only for "special ones".
However, I would still want a way to associate a name with a
revision-number that was simply an alias for the revision-number
and didn't create a new copy in the pathspace because I don't
want that level of visibility for every commit - just the
ability to use a pseudonym for global revision number. The
example I gave of a 'NAME=' revision keyword would do this,
and (unlike a property I assume?) be able to be used in
revision ranges given to svn log and svn diff.
Brad Appleton <email@example.com> www.bradapp.net
Software CM Patterns (www.scmpatterns.com)
Effective Teamwork, Practical Integration
"And miles to go before I sleep." -- Robert Frost
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Mar 23 23:38:30 2004