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

Re: help me show others that there are valid reasons for not supporting a $log$ keyword!

From: Steve Povilaitis <stevepov_at_gmail.com>
Date: Tue, 16 Sep 2008 11:05:58 -0400

> Another argument for you (and kind of addressed in the FAQ): in
> Subversion, logs are NOT file-centric. They are based upon the
> revision. It is not possible to pull the log messages for a single
> file. You can pull the log messages for all revisions in which the
> file in question was edited, but you can't differentiate which
> portions of the log message apply to which file (unless you have a
> strict structure to those log messages).

That's a good point - thanks for mentioning it.

> > Also, for every tagged release we do for the customer they're going to
> want
> > an export of the source with the revision log for each file appended to
> the
> > beginning of the file. Have any of you had to do something along those
> lines
> > and would you mind sharing how you accomplished it?
> That makes no sense at all. You should be publishing a single
> changelist saying "here's what changed since your last release."

I agree with you 100%, unfortunately to paraphrase the warden in the movie
Cool Hand Luke "That's the way he wants it, well, he gets it. I don't like
it anymore than you."

I am scheduling a conference with the folks from on high to get a better
understanding of just what they want to accomplish and if there are some
better ways their needs can be met, but It's going to be an uphill battle.
Received on 2008-09-16 17:06:27 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.