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

Re: exporting an uncommited file and keywords

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-02-16 11:41:22 CET

On Monday 16 February 2004 04:40, Ben Reser wrote:
> Exporting an uncommited file gives some confusing and undocumented
> keyword handling:
> $Id: foo -1M 2004-02-16 09:18:31Z (local) $
>
> The -1 makes perfect sense to us developers but is confusing to a user
> who doesn't know that means an unknown or invalid revision number.
>
> Also the (local) is bad, following the time it makes it look like the
> timezone is localtime if you don't look closely.
>
> I think the following output would be better:
> $Id: foo M 2004-02-16 09:18:31Z (unknown) $
>
> or possibly:
>
> $Id: foo U 2004-02-16 09:18:31Z (unknown) $
>
> The U meaning Unknown or Uncommitted... We can drop the M because it's
> redundent if it's not been committed.
>
> Or perhaps:
>
> $Id: foo U 2004-02-16 09:18:31Z $
>
> Which is consistent with our efforts not to make up usernames that don't
> exist for svnadmin.
>
> Thoughts? Whatever we decide I'll be happy to make a patch. I'll also
> patch the book to document the format (unless someone else wants to
> do that).

Yeah, that was just a quick decision at the time (using '(local)' as the
author). The goal was to know that the version wasn't marked in the
repository.

FWIW, I'm -1 on using 'U' for an uncommitted entity, and 'M' on using one that
has but locally modified. In my mind, it doesn't make it any easier for the
user. I'm fine with removing the author, or using '(unknown)'. Although now
that I think about it, I'd rather we just leave the field blank.

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 16 11:43:18 2004

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.