[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Backing out changes: the prefered method?

From: Sean Russell <ser_at_germane-software.com>
Date: 2002-01-30 20:10:38 CET

Hash: SHA1

On Wednesday 30 January 2002 10:17, Garrett Rooney wrote:
> > ------------------------------------------------------------------------
> > rev 175: ser | Fri 25 Jan 2002 15:34:25 | 1 line
> ahh, i see. each commit didn't actually submit a log entry, so the log
> entry is empty. with an empty entry, svn log prints out '1 line' for the
> length... thus the confusion.

Oh. I assumed that the "1 line" was the number of changed lines, not the
number of lines of the log message. Hm, ok.

An later, Ben Collins-Sussman <sussman@collab.net> wrote:
> 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

Super, thanks. Could you not also do:

  rm <filename>
  svn up -r N <filename>

- --
 |.. "You're young, you're drunk, you're in bed, you have knives; shit
<|> happens."
/|\ -- Angelina Jolie
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org


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

This is an archived mail posted to the Subversion Dev mailing list.