-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Guio <[EMAIL PROTECTED]> writes:
> I wonder whether there is a way to do the following
Yes.
> * Force non empty log when commit (or reject commit if log empty).
Sure. Provide a script for verifymsg to run that checks the log message
size.
can i import empty folder on branch only..
pls give me the way for same...
Thanks
Hridyesh
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Jennifer Vesperman, author of Essential CVS from O'Reily, has
a shell program to lock the repos that you may want to check
out. Check in http://www.oreilly.com/.
-chris
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]
>] On Behalf Of John
>Sent: Sunday, December 12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Feature CVS 1.12.11 has been released. Feature releases contain new
features as well as all the bug fixes from the stable releases. This
version fixes a few minor bugs in both the CVS client and server
executables, as well as extending the write prox
We are doing parallel development with 2 different versions of our
code. We have version 2 on a branch and version 3 is on our main
trunk. What we want to do is update the revision numbers on the
version 2 branch to be 2.xx and the revision numbers on the version 3
trunk to be 3.xx.
I tried to d
Okay, thanks for your quick repy! We were aware that this was
basically a 'cosmetic' fix. We print the CVS log entries in the header
of the files to easily see our changes, so we're seeing the 1.7.2.XXX,
etc and wanted to 'clean it up' a bit so it was easier to read.
I take it we can still go ah
Heather wrote:
Okay, thanks for your quick repy! We were aware that this was
basically a 'cosmetic' fix. We print the CVS log entries in the header
of the files to easily see our changes, so we're seeing the 1.7.2.XXX,
etc and wanted to 'clean it up' a bit so it was easier to read.
It is not a 'c
I guess I should clarify: we didn't just zap the binaries, but we moved them
into a place not in everyone's path. There are a couple of things that still
needed them like ViewCVS. I didn't list all this before because I didn't
think the specific details were important to my original question.
Rachel Suddeth wrote:
> Oh nevermind. I see there is an uncontrolled file by the same
> name in the
> sandbox.
Glad we could help :=)
BTW, with respect to this question:
> > I'm not sure how
> to say if a
> > message came from CVSNT client, or the server running under
> Linux
the first p
hi
before i do something stupid i'd just like to know what would the best
way to fix a major timestamp problem in our repository.
problem
---
about 2.000 files have a timestamp in the year 2011. i basically just
want to touch these files and commit that "change". what is the best way
to do
With cvs 1.10 and local repository access, if you modified files in dir A and
dir B, and then checked them in from the root of the project (without -m), you
would be prompted with your editor of choice for check-in comments for the
changes *for each directory*. What I mean is, you would be prom
Heather wrote:
> We are doing parallel development with 2 different versions of our
> code. We have version 2 on a branch and version 3 is on our main
> trunk. What we want to do is update the revision numbers on the
> version 2 branch to be 2.xx and the revision numbers on the version 3
> trunk
Heh, I think you misunderstood my second message. I meant that we
wanted to make the change for cosmetic reasons, not that it WAS a
cosmetic change. After reading on how the branches are created, I
understand why you don't want to mess with those. However, I don't
understand what the problem is
I ended up using cvs rlog, and I just noticed it wasn't using -n, and it
appears to work fine. Does cvs rlog try to lock the file for some reason, or
is -n just the general rule of thumb for things like these loginfo scripts?
thanks again,
Chris
The 'cvs -n log' command would be running on the
14 matches
Mail list logo
