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

Re: Commit Log File

From: Jonathan Smith <jonsmith_at_members.limitless.org>
Date: 2003-05-13 19:55:01 CEST

Obviously, if developers chose to support both methods, either:

   a) developers support a mechanism that backends both methods with one
      data location, or
   b) users chose one or the other

On 13 May 2003 kfogel@collab.net wrote:

> Jonathan Smith <jonsmith@members.limitless.org> writes:
> > Yeah, I just read the issue report.
> >
> > I've never been happy with using the commands to retrieve the log
> > information this way. Historically, this type of file has been kept and,
> > I prefer it. It's far, far easier to access. But this is oppinion. I'd
> > prefer to support both so people have the choice.
> Consider also the other cost to keeping the file statically:
> information duplication (and hence inevitable divergence).
> Log data can be changed after the commit, using
> $ svn propset -rFOO svn:log ...
> Then the repository log data would be out of sync with your logfile.
> When & how would the logfile get updated? If it's autogenerated, the
> answer is easy: at the next regeneration.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 13 19:53:05 2003

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.