Re: Patch for making CommitID configurable

[Peter Backes]

Hi,

On 27 Apr 2005 at 3:21, Mark D. Baushke wrote:

> It may be worth noting that CVSNT has had this feature for a long time
> and moving to adopt it satisfies a minor goal of trying to reduce the
> separation and entropy between the major CVSNT fork of CVS and the CVS
> that cvshome offers.

I agree that a commit ID might be a handy feature, but the way CVSNT 
did it was merely a quick and dirty hack IMO.  It relies on the 
concept of seconds since epoch, which is not portable.  Further the 
commit ID can only be assumed to be unique for a certain repository, 
so the whole thing cannot be used if somebody wants to build a 
distributed SCM on top of CVS.

I stick to my opinion that currently loginfo provides a much better 
way to achieve what Jim sees CommitID useful for.

> I honestly do not think this feature is the problem you seem to believe.

Even if it isn't, I don't see why it shouldn't be possible to apply 
my patch to let the user decide what he wants.  What is currently 
being done is that users are forced to have CommitIDs even if they 
don't want them (for whatever reason).  This cannot be right.

> If you can provide more consumers of the ,v files that have problems
> using the addition to the format, it would be good to have that list.

Besides rcs, I only remember cvsup as a program that might access the 
files in a CVS directory directly.  However, I don't know if it has 
any problems with the addition to the format, as I don't use it.

-- 
Peter 'Rattacresh' Backes, rtc@helen.PLASMA.Xg8.DE