[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gpg signed commits: new base naming convention
|
From: |
Jim Hyslop |
|
Subject: |
Re: gpg signed commits: new base naming convention |
|
Date: |
Tue, 09 May 2006 09:59:23 -0400 |
|
User-agent: |
Mozilla Thunderbird 1.0.6 (Windows/20050716) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bernd Jendrissek wrote:
> If it will be .#filename.revision, won't cvs get confused when $filename
> ends in something that looks like a revision number?
That is a possibility, yes. However, the naming convention is not new.
It is the same convention used to back up a user's file when an update
produces a conflict, or when a modified local copy is discarded using
'cvs update -C'.
You will have to train your users not to use that pattern, just as you
have to train them not to create directories named 'cvs'.
- --
Jim Hyslop
Dreampossible: Better software. Simply. http://www.dreampossible.ca
Consulting * Mentoring * Training in
C/C++ * OOD * SW Development & Practices * Version Management
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEYKA7LdDyDwyJw+MRAupZAJ9VqrZv9XYRaSATvJrUCPkSmyFN0ACgqRUV
9s0zv6Z7M7z80yPJU+Rr0T8=
=Mbf9
-----END PGP SIGNATURE-----