> > Q: is there a way to get *all* branches, versions,
> > and tags for a file mentioned in the log?
>
> Nope. As a pseudo-hack, you can run 'svn log -v' on a URL that
> represents the root of the repository, and then grep for the filename,
> assuming the filename never changed.
And I suppose that I could do the transitive closure,
following all of the rename and copy messages
forwards and back.
:-(
===
This is going to be a major change in how I use
version control.
I used to try to document branch status in files
like README. As in "look in branch XXX for the
first attempt to make this code run on Windows;
we are not integrating these changes with the
standard UNIX distribution yet".
Trouble was, such comments kept disappearing,
as the README evolved. E.g. checking such comments
in on a branch was almost useless.
But then I realized that I could check such comments
in to the CVS log message. In combination with
cvs2cl.pl, this meant that I could always have access
to documentation about what branches were meant to
do what - what branches were long lived parallel
developments, what branches were task branches that had
been aborted or suspended, but which stiill might
have some useful code, etc.
This global access to branch and version
documentation greatly increased the usability of branches.
Without it: well, I expect that most Subversion users
are from the traditional "branching is dangerous" camp,
IMHO because they have never worked with a tool that
properly supported branches, or because they have never
figured out how to use CVS's limited branching abilities
in a safe way.
Am I right?
===
Brad Apppleton: I know you read this. Have you
figured out good usage models for Subversion yet?
How does it compare to Perforce?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 02:48:25 2004