-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg A. Woods [EMAIL PROTECTED] writes:
There is no trigger for cvs rm and there MUST _NOT_ be.
There is no trigger for cvs add and there MUST _NOT_ be.
Please defend your position for 'MUST NOT' as it seems an entirely
reasonable suggestion that
[ On Thursday, November 18, 2004 at 10:38:44 (-0500), Derek Robert Price wrote:
]
Subject: Re: add hook question (was Re: Problem with importing third-party
sources and adding/committing changes)
Perhaps a -C option to `cvs add' similar to `cvs edit', where -C can
be placed in the user's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg A. Woods wrote:
There is no trigger for cvs rm and there MUST _NOT_ be.
There is no trigger for cvs add and there MUST _NOT_ be.
I have to admit, there is a certain logic to drawing the line at
triggers for repository changes, not workspace
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg A. Woods wrote:
[ On Thursday, November 18, 2004 at 10:38:44 (-0500), Derek Robert
Price wrote: ]
Subject: Re: add hook question (was Re: Problem with importing
third-party sources and adding/committing changes)
Perhaps a -C option to `cvs add
Me Too post
Derek Robert Price wrote:
Greg A. Woods wrote:
There is no trigger for cvs rm and there MUST _NOT_ be.
There is no trigger for cvs add and there MUST _NOT_ be.
I have to admit, there is a certain logic to drawing the line at
triggers for repository changes, not workspace
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Greg,
Is it reasonable to suggest that a addinfo trigger could be run as a
part of the 'cvs commit' command should the client not happen to connect
to the server for a 'cvs add' operation?
The idea would be that having simpler triggers for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Denniston wrote:
I also still would not object to the a `cvs add -C' convenience hook
which requested that the client contact the server and validate the
add. Any team that valued this option significantly should find it
fairly easy to enforce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark D. Baushke wrote:
Hi Greg,
Is it reasonable to suggest that a addinfo trigger could be run as a
part of the 'cvs commit' command should the client not happen to connect
to the server for a 'cvs add' operation?
It should probably run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derek Robert Price [EMAIL PROTECTED] writes:
Mark D. Baushke wrote:
Hi Greg,
Is it reasonable to suggest that a addinfo trigger could be run as a
part of the 'cvs commit' command should the client not happen to connect
to the server for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark D. Baushke wrote:
For that matter, I would like to see disconnected 'cvs diff' commands
where possible for users that already have a CVS/Base/* version of the
file around...
Yep. I'm actually tempted to have the CVS client always create
--- Forwarded mail from [EMAIL PROTECTED]
[ On Wednesday, November 17, 2004 at 09:19:18 (-0800), Paul Sander wrote: ]
Subject: Re: add hook question (was Re: Problem with importing third-party
sources and adding/committing changes)
It depends on the nature and extent of the changes. I can
--- Forwarded mail from [EMAIL PROTECTED]
[ On Thursday, November 18, 2004 at 10:38:44 (-0500), Derek Robert Price
wrote: ]
Subject: Re: add hook question (was Re: Problem with importing third-party
sources and adding/committing changes)
Perhaps a -C option to `cvs add' similar to `cvs edit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander [EMAIL PROTECTED] writes:
We've already discussed how to add such a capability in such a way that
it involves zero overhead for those who don't want it: Register no
triggers and defer their enforcement until commit time. But for
--- Forwarded mail from [EMAIL PROTECTED]
Greg A. Woods wrote:
There is no trigger for cvs rm and there MUST _NOT_ be.
There is no trigger for cvs add and there MUST _NOT_ be.
I have to admit, there is a certain logic to drawing the line at
triggers for repository changes, not workspace
--- Forwarded mail from [EMAIL PROTECTED]
Derek Robert Price [EMAIL PROTECTED] writes:
Mark D. Baushke wrote:
Hi Greg,
Is it reasonable to suggest that a addinfo trigger could be run as a
part of the 'cvs commit' command should the client not happen to connect
to the server for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander wrote:
Keep in mind that, although Greg does not acknowledge it, a number
of people in this forum have stated a requirement for an add-time
trigger that could be used for such things as enforcement of naming
conventions and access
--- Forwarded mail from [EMAIL PROTECTED]
Paul Sander wrote:
Keep in mind that, although Greg does not acknowledge it, a number
of people in this forum have stated a requirement for an add-time
trigger that could be used for such things as enforcement of naming
conventions and access
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander wrote:
It's true that add and commit hooks can enforce the same kinds of
policies
as post-conditions of the commit. However, add hooks can enforce things
like naming conventions. I'm working in a shop right now that prefers to
have
--- Forwarded mail from [EMAIL PROTECTED]
Paul Sander wrote:
It's true that add and commit hooks can enforce the same kinds of policies
as post-conditions of the commit. However, add hooks can enforce things
like naming conventions. I'm working in a shop right now that prefers to
have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yamuna Ramasubramaniyan [EMAIL PROTECTED] writes:
I have a problem using a directory name with a space
in it in the modules file.
Can the modules file not support spaces in the
directory name?
Correct.
Spaces in file and directory names are
Hi,
I read it on info-cvs how to change a branchname using cvs admin commands.
I had to change a branch name and by accident I went into the repository(CVS
ROOT) itself and executed the following command :
cvs admin -nNew_Branch_Name:Old_Branch_Name
And it gave me message saying Administering
Godavarthi, Manasa writes:
I had to change a branch name and by accident I went into the
repository(CVS ROOT) itself and executed the following command :
cvs admin -nNew_Branch_Name:Old_Branch_Name
And it gave me message saying Administering each module_name
I am not sure if I erased
Hello,
I have a problem using a directory name with a space
in it in the modules file.
I have the following line in my modules file:
Docs -d Eng-us Docs_src/Help\ Files
When I do cvs -d /home/cvs checkout Docs, I get an
error:
cvs [checkout aborted]: there is no repository
{page:Section1;} --
Hi Derek,
One Small Question? Can I convert the PVCS archives 6.8 on Windows
2000 to CVS archives in Linux from the script?
Because Script is on LINUX box and How I give it the windows archives ?
Thanks in advance
Pars
Derek
- --
*8
Title: question about rtag command.
That
works for the trunk, but I was looking at being able to tag the status of a
branch
at a
specified date/time.
Harold
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of
Stuart StevensSent: Tuesday
Title: question about rtag command.
Is it possible (with cvs 1.11.x) to tag a branch by date?
I've tried a couple of permutaions of
cvs -q rtag -r branchtag -D datestring modulename
But I'm not sure if it is doing what I think it's doing.
Harold Lynch
Title: question about rtag command.
Normally you would use
Cvs q rtag -D datestring
new tag module to tag
Stuart
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lynch, Harold
Sent: Tuesday, November 09, 2004
12:09 PM
To: [EMAIL PROTECTED]
Subject: question
Hi
I have a question about merging. I thought merging
with two -j options was 'from' revision and 'to'
revision.
This is what happened in my working area from trunk.
I have a file soa.pc, branched out at 1.2, now at
revision 1.2.4.1 on branch, and 1.2 on trunk. I
check-out from trunk, then do
Jeeva Sarma [EMAIL PROTECTED] wrote:
I have a file soa.pc, branched out at 1.2, now at
revision 1.2.4.1 on branch, and 1.2 on trunk. I
check-out from trunk, then do
[ ... ]
cvs update -j 1.2 -j 1.2.4.1 soa.pc
Yes, like that. The command means, merge all changes
that occurred between 1.2
Now, I was reading a material about CVS technology and
I came across some doubts in concerns the some
concepts:
1-To take place the transfer of the files stored in
the repository q they were modified for your work
area, through a sicronização operation. Like this,
would to be in fact that
Gleidson S? Barreto [EMAIL PROTECTED] wrote:
1-To take place the transfer of the files stored in
the repository q they were modified for your work
area, through a sicroniza??o operation. Like this,
would to be in fact that sicroniza??o operation?
I'm not sure what you mean, but...
I'm trying to set permissions for a projectd using chacl and am unable
because the initial cvs checkout is apparently not work. We have a
large repository with many projects in place, and I've been using cvs
checkout for months now, usually for deployments and tagging; but for
some reason in this
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of JeffreyC
Sent: Tuesday, 14 September 2004 10:40 AM
To: [EMAIL PROTECTED]
Subject: Question about chacl
I'm trying to set permissions for a projectd using chacl and am unable
because the initial cvs checkout is apparently not work. We have
Title: question about helping cvs performance.
I'm getting complaints from the users about the amount of time it takes to
do a tag or a branch (especialy the branch).
Are there any standard things that can be done, or to watch out for, that
would make these functions run as well
Title: rtag question
will the command:
cvs -q rtag -D 2004-08-09 2:00 GMT -r SOMEBRANCHTAG SOMEMODULE
put a tag on branch SOMEBRANCHTAG as the files were at 2am GMT on August 9th 2004 ?
I was warned that tagging by date had problems on branches.
The version of cvs we are using
Title: Question about process scheduling - revisited.
I originally had a question about the way cvs server process get scheduled.
Let me elaborate.
The setup:
Server:
DELL dual intel processor (2.0 gig hertz).
4 gig ram
500 gig harddriver.
Dual gigabit and 10t network
-d $CVSROOT checkout sv;
CVS update is done by:
cd /SOMEWHERE/sv;
cvs -d $CVSROOT update -dP;
CVS commit is done by:
cd /SOMEWHERE/sv;
cvs -d $CVSROOT commit;
I describe all this because I dunno if you might need this information to answer me
the following question:
I
K. Posern [EMAIL PROTECTED] writes:
But I need an exact copy of the version a CLIENT has in its
/SOMEWHERE/sv dir on the SERVER (so without the rcs stuff).
How can I achieve this? Do I have to to do an cvs-checkout on the
server and cvs-update everytime a client did commit something?
Or
/SOMEWHERE/sv;
cvs -d $CVSROOT commit;
cvs -d $CVSROOT makes little sense... cvs uses $CVSROOT by default
I describe all this because I dunno if you might need this information to
answer me the following question:
I thought that the CVS-Tree LOCAL and on the SERVER are IDENTICAL (after I
did
Hello,
* On Thu, Aug 26, 2004 at 12:20:14PM +0200 K. Posern wrote:
But I need an exact copy of the version a CLIENT has in its
/SOMEWHERE/sv dir on the SERVER (so without the rcs stuff).
Have a look at C.3.5.2 of your manual:
Title: Question about process scheduleing
I'm trying to look into a problem with the amount of time it takes us to do a checkout of a large (800 meg) module.
On most of the machine in the shop it takes between 10 and 15 minutes, on one machine it can take an hour.
When I look at top
K. Posern wrote:
But I need an exact copy of the version a CLIENT has in its
/SOMEWHERE/sv dir on the SERVER (so without the rcs stuff).
How can I achieve this? Do I have to to do an cvs-checkout
on the server and cvs-update everytime a client did commit
something?
Or can I say to the server
Lynch, Harold wrote:
I'm trying to look into a problem with the amount of time it takes us to
do a checkout of a large (800 meg) module.
On most of the machine in the shop it takes between 10 and 15 minutes,
on one machine it can take an hour.
When I look at top on the cvs server, the process
Lynch, Harold wrote:
I'm trying to look into a problem with the amount of time it takes us to do
a checkout of a large (800 meg) module.
On most of the machine in the shop it takes between 10 and 15 minutes, on
one machine it can take an hour.
When I look at top on the cvs server, the
Lynch, Harold writes:
On most of the machine in the shop it takes between 10 and 15 minutes,
on one machine it can take an hour.
Look for network problems with that machine -- that sounds like dropped
packets and retransmissions.
-Larry Jones
Yep, we'd probably be dead by now if it wasn't
Menu-View-Output
John E wrote:
Just a clarification, I refereing to the output window when I said
status window.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
On my all but one of my Windows machines I can see the docked status window.
On one, I cannot. How do you make this window visible?
Thanks
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Just a clarification, I refereing to the output window when I said
status window.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Hi
I have a question concerning commitinfo and project standards. Is it
possible to run an app (called by commitinfo) against a particular file in
a specific sandbox at commit time? I'm trying to prototype a stylechecker
and don't want anyone but myself affected initially.
If this is possible
At 12:41 PM 8/5/2004, Tennis Smith wrote:
I have a question concerning commitinfo and project standards. Is it
possible to run an app (called by commitinfo) against a particular file in
a specific sandbox at commit time? I'm trying to prototype a stylechecker
and don't want anyone but myself
At 12:53 PM 8/5/2004, Frederic Brehm wrote:
It's probably easiest to create a new temporary and test your commitinfo
script in there.
That should be a new temporary REPOSITORY
Sorry,
Fred
___
Frederic W. Brehm, Sarnoff Corporation,
Frederic Brehm [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
At 12:41 PM 8/5/2004, Tennis Smith wrote:
I have a question concerning commitinfo and project standards. Is it
possible to run an app (called by commitinfo) against a particular file
in
a specific sandbox at commit time
Hi,
I have a single file that's pivital to a project. Any time that file is
updated, we need to do a re-compile of the components dependent on it. Is
there any way to automatically drive the recompilation when the user does
a cvs update on that central file?
Any examples are welcome too. ;-)
The most obvious suggestion to me is add a dependency rule to your makefile
for this file that executes a cvs update important_file.c command. That
way any time you do a make on the project, the critical file will be updated
and recompiled if it has changed. For this to be useful, you must be
When I do a cvs import of a new vendor version the new files become the
head revision. I'd like to do the import such that it doesn't affect HEAD.
Only after I've tested the new stuff I want it to become HEAD. Of course,
it should work with local changes merged in just like the standard way of
I had same problem some time back but don't have any solution to it..
you can go through
http://lists.gnu.org/archive/html/info-cvs/2004-02/msg00077.html
-Rohan
Lemke, Michael IZ/HZA-IOP wrote:
When I do a cvs import of a new vendor version the new files become the
head revision. I'd like to do
Lemke, Michael IZ/HZA-IOP writes:
When I do a cvs import of a new vendor version the new files become the
head revision. I'd like to do the import such that it doesn't affect HEAD.
Only after I've tested the new stuff I want it to become HEAD. Of course,
it should work with local changes
Test BEFORE importing!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Larry Jones
Sent: Thursday, July 22, 2004 10:12 AM
To: Lemke,Michael IZ/HZA-IOP
Cc: '[EMAIL PROTECTED]'
Subject: Re: Import question
Lemke, Michael IZ/HZA-IOP writes:
When I
From: Christopher.Fouts
Sent: Thursday, July 22, 2004 4:22 PM
To: [EMAIL PROTECTED]
Subject: RE: Import question
Test BEFORE importing!
Sure but I need the merge of the local changes. But I can't get them
without the import or can I?
-Original Message-
From: [EMAIL
]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Lemke, Michael IZ/HZA-IOP
Sent: Thursday, July 22, 2004 10:36 AM
To: [EMAIL PROTECTED]
Subject: RE: Import question
From: Christopher.Fouts
Sent: Thursday, July 22, 2004 4:22 PM
To: [EMAIL PROTECTED]
Subject: RE: Import question
Test BEFORE
-Original Message-
From: Christopher.Fouts
Sent: Thursday, July 22, 2004 4:43 PM
Subject: RE: Import question
Can you export (not check out) the latest files you need
from a current vendor branch, which should contain the changes
you want (correct), add (not cvs add) your new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lemke, Michael IZ/HZA-IOP [EMAIL PROTECTED] writes:
When I do a cvs import of a new vendor version the new files become the
head revision. I'd like to do the import such that it doesn't affect HEAD.
Only after I've tested the new stuff I want it
From: Mark D. Baushke
Sent: Thursday, July 22, 2004 5:16 PM
To: Lemke, Michael IZ/HZA-IOP
Cc: '[EMAIL PROTECTED]'
Subject: Re: Import question
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lemke, Michael IZ/HZA-IOP writes:
When I do a cvs import of a new vendor version the new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lemke, Michael IZ/HZA-IOP [EMAIL PROTECTED] writes:
However, this whole thing makes me realize I
don't really understand vendor branches. What's
different from ordinary ones?
The vendor branch more closely models the RCS
branching model. The
Lemke, Michael IZ/HZA-IOP [EMAIL PROTECTED] wrote:
When I do a cvs import of a new vendor version the new files become the
head revision. I'd like to do the import such that it doesn't affect HEAD.
Only after I've tested the new stuff I want it to become HEAD. Of course,
it should work with
Hi all,
I want to some operations after commit process is done. If I invoke
cvs add, I do not do anything. Currently, I add the operation in
loginfo file but my operations will get trigger if I run cvs commit or
add.
If I just want to trigger my operation once the cvs commit is done,
how to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hon Seng Phuah [EMAIL PROTECTED] writes:
I want to some operations after commit process is done. If I invoke
cvs add, I do not do anything. Currently, I add the operation in
loginfo file but my operations will get trigger if I run cvs commit or
How can I perform a diff between 2 dates in a given branch? I was hoping
something like Branch:Date would work the same way it does for the `cvs
up -j' option, but it is not recognized?
Anything I'm missing?
Manu
PS: I'm using the client cvs 1.10.5
My question is:
I have four subdirectories in a CVS repository, such as:
+-a
|--b
|--c
|--d
If the a/b/c module contains a few files. If I want to add new module
using an empty hard drive, I will have to invoke cvs co a/b/c first.
Only then I invoke cvs add directory command
Hon Seng Phuah writes:
Unfortunately, by invoke checkout command, it will checkout all a/b/c
module files into my new hard drive. Is there a way to prevent
checking out all module files into my new hard drive?
Use the -l option of checkout to prevent recursion.
-Larry Jones
I keep
[EMAIL PROTECTED] wrote:
Jeeva Sarma writes:
I have a question using cvs admin command to delete a revision of a
file. If I deleted revision 1.7 of a file, which also exists on a
branch at that revision, what will be the status of that
file on the
branch?
A revision cannot
Title: branch removal question
I
asked this question last Friday but got no response.
Was it
poorly asked, not enough information, too
ignorant for words? If I need to supply more
information
please
let me know, I would be glad to.
Thanks,
Don
Butts
-Original Message-From
Don Butts wrote:
I asked this question last Friday but got no response.
Was it poorly asked, not enough information, too ignorant for
words?
How about, this requires a few more brain cycles than were available at the
time? :=)
-Original Message-
We are using cvs
not create preprod`date +%Y_%b_%d` branches when you want to go into QA,
so you have all the information that lead up to each release.
(next question is a more personal process, not general practice) and why are
the production releases not just (normal) tags on the QA branch(es), where the
QA people have
be
forgotten.
--- Forwarded mail from [EMAIL PROTECTED]
I asked this question last Friday but got no response.
Was it poorly asked, not enough information, too
ignorant for words? If I need to supply more information
please let me know, I would be glad to.
-Original Message-
From: Don
--- Forwarded mail from [EMAIL PROTECTED]
Don Butts wrote:
I asked this question last Friday but got no response.
Was it poorly asked, not enough information, too ignorant for
words?
I wouldn't remove the branches. I'm always reluctant to remove anything from
the history.
Instead
[EMAIL PROTECTED] wrote:
Floating tags can also be used. For example, create a tag
called PRODUCTION and apply it to the next release. Then
just run cvs update
in the production area, and the proper versions will appear.
Yep, that's basically the idea I was trying to get across.
The down
I have a question using cvs admin command to delete a
revision of a file. If I deleted revision 1.7 of a
file, which also exists on a branch at that revision,
what will be the status of that file on the branch?
Some files exist on trunk and also branch, and we want
to rollback some revisions
Jeeva Sarma writes:
I have a question using cvs admin command to delete a
revision of a file. If I deleted revision 1.7 of a
file, which also exists on a branch at that revision,
what will be the status of that file on the branch?
A revision cannot be on multiple branches. Revision 1.7
Title: branch removal question
We are using cvs in somewhat of a non-standard way.
We have a production cut of our compiled source that
we deploy via cvs using a production branch. The
application does not mind the fact the CVS control
files co-exist within the source and the application
:17:10 -0400
From: [EMAIL PROTECTED]
Subject: RE: newbie question on initializing repository
To: [EMAIL PROTECTED]
In this case, I'd import a blank project, and then use cvs add
in a
script to add the
files, using the -kb option accordingly. Here's a c-shell pseudo-code
# Assume *.h and *.cpp
Hello, I wonder if anyone can help me.
I am after a list of Tags made in CVS.
Looking at the documentation I got the impression I should be viewing the
Taginfo file, but it doesn't give me the information that I want.
Can anyone help me please because I think I am well off the mark at the
Iain Freeston [EMAIL PROTECTED] writes:
I am after a list of Tags made in CVS. Looking at the documentation
I got the impression I should be viewing the Taginfo file, but it
doesn't give me the information that I want.
A list of tag names is stored in the CVSROOT/val-tags file in the
Iain Freeston wrote:
Hello, I wonder if anyone can help me.
I am after a list of Tags made in CVS.
Looking at the documentation I got the impression I should be
viewing the Taginfo file, but it doesn't give me the
information that I want.
Can anyone help me please because I think I am
Jim.Hyslop writes:
Be
aware that val-tags shows all the tags ever applied to any file in the
repository
No, it doesn't. It shows all the tags that have been used to *retrieve*
files from the repository since the val-tags file was created. It's
just an optimization -- you can delete it at
Brian Gough writes:
A list of tag names is stored in the CVSROOT/val-tags file in the
repository.
But it's not complete. It's just a cache for optimization purposes.
-Larry Jones
Everything's gotta have rules, rules, rules! -- Calvin
___
Iain Freeston writes:
I am after a list of Tags made in CVS.
Tags are kept in the individual RCS files, there's no central database
of them. You can find the tags on a particular file with the log
command or with status -v.
-Larry Jones
I stand FIRM in my belief of what's right! I REFUSE
Hello everyone,
I am reasonably new to CVS and am looking for some tips/handy hints for upgrading the CVS server. can anybody give me any help or advice please ?
my OS is :
SunOS xultra1 5.8 Generic_108528-15 sun4u sparc SUNW,Ultra-2System = SunOS
Node = xultra1
Release = 5.8
Thanks in
Download the latest source, unpack it, cd into the directory:
./configure
make
su
make install
(Some systems allow sudo make install)
HTH
Alex
Am 10.06.2004 um 12:16 schrieb mark hanna:
Hello everyone,
I am reasonably new to CVS and am looking for some tips/handy hints
for upgrading the CVS
Alex v.Below writes:
Download the latest source, unpack it, cd into the directory:
./configure
make
su
make install
cvs init
It hasn't been strictly required so far, but it's a good idea. It gives
the new CVS a chance to update the existing repository should the format
change, add new
Hello,
* On Mon, Jun 07, 2004 at 05:34:02PM -0400 Larry Jones wrote:
However, I now believe its not that simple, as the binary
files(only) must be initialized with the -kb option. Is that
correct? If so, any suggestions on the simplest/easiest to go about
this?
If you can distinguish
Hello,
This is a first time user question.
We have collected all of our source
files within a directory structure and are ready to initialize the cvs
repository. There are a couple
thousand files. Roughly 20% are binary type files and are scattered
around throughout various directories.
My
ion though
-chris
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Bret A CooperSent: Monday, June 07, 2004 4:47
PMTo: [EMAIL PROTECTED]Subject: newbie question on
initializing repositoryHello, This is a first time
user question. We have
Bret A Cooper writes:
My original plan was to run the cvs init command from the topmost
directory and be done.
I think you mean cvs import -- init just creates a repository, it does
not populate it with user files.
However,
I now believe its not that simple, as the binary files(only) must
Hello,
I'm new to CVS andI would like to install a
cvs server on a linux worksation and a cvs client on a WinXP workstation. I
would like to access the cvsserver with a secure protocol.
What are the tools (cvs, wincvs, cvsnt, ...) and
protocol (gserver, ssh,...) which are required or best
with an ssh tunnel.
The archives of this group should give you ample info on this.
As to anonymous read access, I pass the question to the rest of the group. I have no experience with this as it is none of my requirements.
HTH
Alex
Am 03.06.2004 um 14:09 schrieb Jean LEE:
Hello,
I'm new to CVS and I
?
will it ever be 2.1 and so on without our explicitly
making it so using the -r on check-in?
And I have a question about 2 files that are on the
same branch and have logs as below
RCS file:
/cvsrep/cvsroot/OP/op/asos/src/java/com
Mala T writes:
I have 2 questions about version numbers. First, is
there any limit on the number of versions we can have
for a file in cvs?
Only the maximum value of an integer on your system and the amount of
disk space you have available to hole the repository.
will it ever be 2.1 and so
Alex v.Below writes:
If you need to control read/write permissions, I suggest a pserver
combined with an ssh tunnel.
There's usually no need for such complication, just use pure ssh with
normal OS permissions to control access.
-Larry Jones
What a waste to be going to school on a morning
Hi,
I have a rather specific issue here:
Suppose we have created a branch for a development in our
module called branch_A for a longer time. During the
development we have decided to intagrate all changes on the
main branch into branch_A (and we have tagged both the
main/HEAD and the branch).
101 - 200 of 1046 matches
Mail list logo
