[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patch for making CommitID configurable

From: Derek Price
Subject: Re: Patch for making CommitID configurable
Date: Mon, 25 Apr 2005 16:59:09 -0400
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Peter Backes wrote:

>On 21 Apr 2005 at 10:02, Derek Price wrote:
>>I really want to make this the default behavior, even after an
>>upgrade.  Would this do the trick for you?
>What do you mean exactly?  new->use_commit_id = true instead of
>false, i.e. have commit IDs written even for old repositories after
>an update?  I'd not recommend this.  It violates the principle of
>least astonishment (like the current solution).  However, at least it
>was better than the current situation.

I'm not sure I believe that.  I think most people would prefer to not
have to jump through any hoops to see new features enabled, especially
when dealing with feature releases, and I don't think all that many
people run RCS inside their CVS repositories anymore.  Any dissenting
opinions other than Peter's out there?

Why is RCS whining anyhow?  The spec leaves room for newphrases.  Is it
requesting an upgrade?



Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]