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

Re: [PATCH] Add -cHEAD support (issue #3041)

From: Charles Acknin <charlesacknin_at_gmail.com>
Date: Wed, 20 Feb 2008 18:33:27 +0100

On Wed, Feb 20, 2008 at 5:37 PM, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> Hi Charles.
> Why do you want to add "-cHEAD", and most importantly, what do you want it to mean?

Basically for the following reason: users may expect -c to use the
same arguments as -r since -cREV is a shortcut for -rREV-1:REV. As I
said in a previous post it occurred to me to type "svn di -cHEAD"
after I've seen someone committing on #svn-dev. It may be me being
lazy to type the rev in, but I think I've wanted this feature for the
sake of homogeneity between options. I understand this might not be
the most used feature ever.

> "-r HEAD" always means the latest revision (current state) of whatever targets
> we're looking at.
> If "-c HEAD" is supposed to mean
> "{repository-youngest-rev - 1}:{repository_youngest_rev}"
> then, on most branches, most of the time, it evaluates to a null change,
> because the repository youngest revision didn't change whatever branch we're
> looking at. That's not useful in general.

That's what the patch is implementing, yes. As you point out, using
-cHEAD will be a no-op when executed in a sub-directory (branch or
whatever) below which no change happened. But when executed from the
very root of the repository or when passing it as target (could be
../../ as much as http://path/to/repos), it will always return some


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-20 18:33:41 CET

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.