Because the 'svn log <filename>' use-case doesn't work yet, what
you're seeing instead is just 'svn log', which simply prints the log
message for every revision.
But to answer your question: once we fix this use-case, yes, your
algorithm is the right way to back out changes to a file. You would
view the log for the *one* file, determine that you want to backdate
the file to revision N, and then do something like:
svn diff -r N -r HEAD <filename> | patch
svn commit
Or you could use 'svn merge' command, which will be something
extremely similar.
Sean Russell <ser@germane-software.com> writes:
> On Wednesday 30 January 2002 08:53, Ben Collins-Sussman wrote:
> > Changed by one line for every single revision? I don't think you saw
> > what you think you saw. Or if you did, I'm worried. Can you be more
> > specific?
>
> ser@valentine Work/rexml/test $ svn log core_test.rb
> ------------------------------------------------------------------------
> rev 177: ser | Mon 28 Jan 2002 14:21:41 | 1 line
>
>
> ------------------------------------------------------------------------
> rev 176: ser | Sun 27 Jan 2002 07:46:27 | 1 line
>
>
> ------------------------------------------------------------------------
> rev 175: ser | Fri 25 Jan 2002 15:34:25 | 1 line
>
> ...
>
> and so on, back to revision 1.
>
> --
> |.. The only underprivileged minority in America today are the poor.
> <|> --- SER
> /|\
> /|
> |
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:01 2006