Colm Aengus Murphy wrote:
We've come across the following funny when using the cvs
editors feature.
In my workspace I do a cvs edit to indicate I am editing a file.
cvs editors correctly reports me as an editor.
If I then create another workspace using cvs co and run
cvs editors
I am no
On Mar 24, 2005, at 7:00 AM, [EMAIL PROTECTED] wrote:
Colm Aengus Murphy wrote:
We've come across the following funny when using the cvs
editors feature.
In my workspace I do a cvs edit to indicate I am editing a file.
cvs editors correctly reports me as an editor.
If I then create another
Paul Sander wrote:
You don't have to store the actual locations in the
repository. (Doing
so is pointless anyway given that mount points can appear and
disappear
non-deterministically.) Just store an identifier there,
[etc]
Thank you for corroborating how difficult this would be to
Dear all,
I am happy to announce a new version of the CVS ACLS WEB interface.
You can download it from http://cvsacls.planck.fr
Release notes:
- Few bugs corrected (e.g: commit automatically enabled if admin right
is given, ...)
- In the configuration file you can choose to execute all cvs
I understand how verifymsg can be used to check the text in a commit
message. The problems is that I'd like to have different checks for
different branches, and there is no branch name variable that I can
see to pass into a script called from verifymsg.
So I went to see how scripts such as
Google for the verifymsg script thread on suggestions
how to get the branch name during a commit for the
verifymsg.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Matt Doar
Sent: Thursday, March 24, 2005 3:04 PM
To: info-cvs@gnu.org
Cc: [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Matt,
Matt Doar [EMAIL PROTECTED] writes:
I understand how verifymsg can be used to check the text in a commit
message. The problems is that I'd like to have different checks for
different branches, and there is no branch name variable that I
/attachments/20050324/a37d150f/at
tachment.html
--
Message: 2
Date: Thu, 24 Mar 2005 14:37:28 +
From: Colm Aengus Murphy [EMAIL PROTECTED]
Subject: cvs editors funny
To: info-cvs@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii; format
SUBRAMANIAN, SARAVANAN (SBCSI) writes:
We use branches in CVS, When we do merge the conflicted files which are
merged earlier appears again and again.
How to solve this issue.
Don't keep merging the same changes over and over:
