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

[PROPOSAL] sane log/diff behavior on single revision (was: svn commit: r31104 - trunk/tools/client-side)

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Thu, 08 May 2008 18:17:00 -0400

kfogel_at_tigris.org writes:
> * tools/client-side/showchange.pl: Default to repository root for the
> URL, so people never have to cd to get the result they want.

This was obviously a good change for showchange.pl. I'm wondering if it
might be a good idea for the command-line client too!

Right now, if you run 'svn log -rNNN' or 'svn diff -cNNN' in a working
copy directory, you may or may not get all of rNNN, even though rNNN was
committed in that repository.

   1) If rNNN was committed to some other branch, and never merged to
      this working copy's branch, then you'll get no output (well,
      you'll get a "------------" line in the case of log, but that's
      the same as getting no output).

   2) If rNNN was committed above the current directory, but includes
      some stuff in or under the current directory, then you'll see that
      subset of rNNN, but not the whole thing.

   3) If rNNN was committed to some other branch, but merged to the
      branch for which cwd is a working copy, then you'll see rNNN,
      except perhaps as adjust according to (2).

I think that's all more or less correct. Can you keep it straight? I
sure can't. I'm not even sure about the last part of (3), but I'm not
going to bother to test it, because I have a better behavior to propose

   If the user explicitly requests a single revision but not a path,
   then show all of that revision, by using cwd's "Repository Root"
   as the URL.

Would that *ever* be the wrong thing to do?


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-09 00:17:12 CEST

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.