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

Re: line-ending conversion and keyword substitution

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2001-12-11 18:00:56 CET

Max,

We're not supporting $Log$ (this was one of the few things this list
has ever achieved near-unanimous agreement on :-) ), so it won't be a
problem.

In fact, quite a few of the CVS/RCS keywords are meaningless for
Subversion, and others may mean something subtly different. But
that's for another post.

-Karl

Max.Hyre@cardiopulmonarycorp.com writes:
> Dear Subversives:
>
> In the keyword-handling description, we note:
>
> > - When committing, if the property is 'on', then an
> > un-substituted copy will be sent to the repository.
>
> This whole design is great, but I don't see addressed in the
> mail or in DESIGN (at least the [identical?] versions found
> a) under the `Docs' tab, and b) in the tarball) the question
> of how to respond if the keyword expansion data have been
> modified.
>
> My main use of such is when I'm moving code from a private
> development branch to one shared with other developers: I
> typically trim the log entries added on my branch, and summarize
> them into one entry for the shared branch.
>
> This is the least-troublesome aspect, because it looks as if
> $Log$ expansions just add the entry and abandon it (i.e., don't
> remove or rework it on commit, but just keep prepending to it).
> If the contents of a $Id$ or $Source$ keyword, say, are changed
> between checkout and commit, what's the answer?
>
> My first impulse is to notify the user and abandon the commit.
> I'm not sure what anyone could want by doing such, so maybe SVN
> should just warn the user and dispose of the modified content?
>
> I'll let wiser heads chew this one over...
>
> --
>
> Best wishes,
>
> Max Hyre
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:52 2006

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.