[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 23:52:44 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 30 January 2002 13:35, you wrote:
[long example snipped]
> > Am I too verbose? :-)

Not at all. I love examples. Lately, I've taken to documenting all of my
methods with usage examples, rather than descriptions.

Anyway, thanks for the clarification.

How will diffs on directories show up? At the moment if I have:

        A/x

and I do:

        svn mv A B
        svn ci && svn up
        echo "blah" >> B/x
        svn ci

diffs get all messed up. I can't do a diff -r on x or B; again, I'm assuming
that this will eventually be fixed, so I'm not worried. However, I'm trying
to imagine what an 'svn diff -r B' would look like.

At the risk of overloading the topic, some of these reply lists are getting
rather long; what are the rules for CC'ing messages? I'm subscribed to list,
of course, and I'm getting duplicates of everything that I'm involved in a
discussion of. I assume that the reason that CC'ing individuals on the list
is in case somebody isn't subscribed. Is everybody just deleting duplicates?

- --
 |.. "Democracy is freedom only when the majority are tolerant -- which
<|> is never."
/|\ -- Clayton E. Cramer
/|
 |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8WHk9P0KxygnleI8RAs8xAJ9BqG4L9wC++ikujhtvNn8iG5N0gQCgpocL
FdPFtwI2YVJlu2Y2BVyLRlY=
=I7C8
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
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.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.