git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Karl Hasselström" <kha@treskal.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Sam Vilain <sam@vilain.net>, git@vger.kernel.org
Subject: Re: [PATCH] git-svn: handle changed svn command-line syntax
Date: Sat, 22 Sep 2007 11:06:17 +0200	[thread overview]
Message-ID: <20070922090617.GA6817@diana.vm.bytemark.co.uk> (raw)
In-Reply-To: <20070921082348.GA5152@mayonaise>

On 2007-09-21 01:23:48 -0700, Eric Wong wrote:

> The @REV and -rREV distinction/ambiguity has always confused me in svn,
> too.  It always seems that it needed to be one way sometimes, the other
> way at other times, and even _both_ at other times...

-rREV specifies the operative revision, and @REV specifies the peg
revision. See the clear but dreadfully long explanation here:

  http://svnbook.red-bean.com/en/1.4/svn.advanced.pegrevs.html

In short, it's a way to manage the complexity that comes from
considering files (and directories!) to have an identity that is
preserved across copies and renames.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle

  reply	other threads:[~2007-09-22  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21  2:02 [PATCH 0/3] git-svn: pass tests on svn trunk Sam Vilain
2007-09-21  2:02 ` [PATCH] git-svn: fix test for trunk svn (commit message not needed) Sam Vilain
2007-09-21  2:02   ` [PATCH] git-svn: fix test for trunk svn (transaction out of date) Sam Vilain
2007-09-21  2:02     ` [PATCH] git-svn: handle changed svn command-line syntax Sam Vilain
2007-09-21  3:15       ` Sam Vilain
2007-09-21  3:27         ` Sam Vilain
2007-09-21  8:23           ` Eric Wong
2007-09-22  9:06             ` Karl Hasselström [this message]
2007-09-21  8:27 ` [PATCH 0/3] git-svn: pass tests on svn trunk Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070922090617.GA6817@diana.vm.bytemark.co.uk \
    --to=kha@treskal.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    --cc=sam@vilain.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).