Re: Way to get current revision as keyword...?

On Sat, Dec 04, 2004 at 05:59:10PM -0000, Max Bowsher wrote:
> But what about when the entire WC is not at a single revision?

Hrm. In thinking about the response, I do see where the issues may get
a bit tricky.

Here's my thinking about this question:

- Checkout revision 100. Substitute "100" for all files.
- Changes occur remotely, up to revision 103.
- Make updates locally and commit, those files get revision 104.
  Subtitute "104" for all files which were committed.
- "svn update" to pull in remote changes. Substitute "104" for all files.

> Or, if you "svn update" only parts of a working copy?

You would only update substitutions where appropriate. So:

- Checkout revision 100. Substitute "100" for all files.
- Changes occur remotely in directories "a", "b", and "c", up to
  revision 103.
- "svn update" in directory "a". Substitute "103" for all files in "a".

> And what about local modifications? svnversion will tell you about them, but
> there's no way a keyword could do that.

From what I can tell, keywords aren't updated for local modifications,
so I don't expect that to change.

-- 
Randomly Generated Tagline:
Another way to look at it is that screensavers are sort of a poor man's
 LSD, without the bad trips.
              -- Larry Wall, 8th State of the Onion