Karl Fogel <firstname.lastname@example.org> writes:
> First of all, it's not too late. It doesn't matter what way you've
> solved or failed to solve the problem -- this is a revision control
> system, the old foo is still there, and anything that would have
> retrieved/copied it yesterday will still work today.
Yes, i know.
> So the "at the time I would have revived it" and "now, after already
> screwing up" are negative thinking, bad karma, and all that :-).
Not really. They're part of my example.
> Do your log messages say when you removed it, if you can search
> through a range of them?
The log messages of the old /foo say it. One of the issues here
is how to get at the old /foo.
> > But there are a other ways to get here. Maybe this /foo and the
> > old /foo *aren't* related, but nevertheless i want the old history.
> > I point this out so that when thinking about this problem people
> > won't assume that you should always svn cp -r; not necessarily.
> I don't understand what this means.
Sorry, i don't know if i can explain it better. There may be two
unrelated files called /index.html, for example. One was removed
6 months ago. Another was created today. Unlike the first use
case, in this one they are not related. Nevertheless, we may want
to access the history of the first /foo.
> restrictive. If CVS did what SVN does, CVS would be have this
> interface issue too.
I'm well aware, but that is not relevant. CVS doesn't do what svn
does, so it is easier in this use case. Unless an option is added
to svn log, in which case it wouldn't be easier in cvs after all.
Hope i'm not confusing anyone :).
> I agree we should offer both 1 and 2. Whether a "--all-revisions"
> flag is the best interface, I'm not sure; at least the name of the
Yes, i don't really care what the option is called. I just needed
something to refer to it if i was going to describe it.
> I prefer:
> svn log --follow-copies /* this one is the default */
> svn log --follow-paths /* like your "--all-revisions" */
> svn log --follow-nodes /* means "none of the above", just stop
> at node creation */
I like this, and i like having --follow-copies as the default.
Eric Gillespie <*> email@example.com
Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jun 28 00:29:37 2002