Re: Commit ID Enhancement

[Derek Robert Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim.Hyslop wrote:

>Derek Robert Price wrote:
>
>>It occurred to me that a "Commit ID" implemented as a tag might make a
>>useful addition to the CVS feature-set.
>
>
>CVSNT has a unique commit ID, but it doesn't look like it's
implemented as a
>tag. The sample log at http://www.cvsnt.org/wiki/MergePoint shows, in
part:
>
>----------------------------
>revision 1.8
>date: 2003/11/06 21:53:13;  author: gstarret;  state: Exp;  lines: +0 -0;
>kopt:
> kv;  commitid: 257f3faac2c9c824;  mergepoint: 1.6.2.1;
>changed for some reason
>----------------------------
>
>Does this come close to what you had in mind?


I suppose.  As long as the commitid would be given special properties
there may not be any good reason to treat it exactly like a tag
otherwise, but there would be some overlap.

What sort of mergepoint processing does CVSNT do?  The link you sent
appears to be down just now.

Derek

- --
                *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAs+/eLD1OTBfyMaQRAg15AKDnXelHc8AYAdvx2gTdtBnrSa9/bQCfZ+Qr
QqbbgLmEjqhI4UOo1yP89zA=
=seba
-----END PGP SIGNATURE-----