-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pierre Asselin <[EMAIL PROTECTED]> writes:
> ... It's important to understand that each
> import after the first *breaks the trunk* until
> the merge has been successfully committed.
Note that if you are using cvs 1.12.x, you may
find the -X option t
What I've done in this scenario in the past is to create an "integration"
branch. NOT a QA branch, but one which the developers only are allowed to
merge to, just to check the viability of their changes. A cruisecontrol
system runs a continuous build on the integration branch, to do both of 1)
I recently found a problem with cvs using; 'cvs diff -r HEAD' for a
module always exits with 1 (checked by 'echo $?'), even if I start in a
empty local directory and do a 'cvs checkout'.
By the way, 'cvs diff' for that problem module exits with 0, which is
normal.
I'm afraid whether it
Hi,
I have a point that confuses me about branches usage.
We have developpers that want to isolate themselves from the trunk, by
creating a branch.
After that, the code needs to go to QA. This is where i'm confused: how can
we make that code go to QA? If we merge the code from the branch to the
Bob Fyfe <[EMAIL PROTECTED]> wrote:
> We receive source code from a vendor which consists of many files
> (call it version 1).
Ok so far.
> That source code requires running a 'make' to
> set up the environment from the tar file they distribute.
Fine, but the 'make' has nothing to do with CVS
On Mon, Feb 21, 2005 at 04:45:56PM -0500, Bob Fyfe wrote:
> We receive source code from a vendor which consists of many files
> (call it version 1). That source code requires running a 'make' to
> set up the environment from the tar file they distribute.
> Subsequently, several files have been c
Well, I've searched the archives and FAQ as best I can and while I
have seen threads similar to the information for which I'm looking,
I did not see exactly this...
I've used CVS over the last year to my own satisfaction...no expert
but useful to me. Our organization now has a new project on th
Hi,
Is there any way to pull out only the "comment" from the CVS- LOG command.
Thanks&Regards
Debi
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Mike Do wrote:
> I am trying to correct an error that was made with our cvs
> repository a
> while back. We have what we consider to be our "main branch",
> which has
> been tagged with the sticky tag R1-0. Most of the files with that
> sticky tag have a working version number in the form 1.1.2.x
Jesper Vad Kristensen wrote:
> That's very interesting. We're working with binary source
> code here and
> have some performance issues when retrieving stuff from
> branches (due to
> the backtracking or whatever it's called).
>
> Would you - or anyone else here - happen to know if storing the w
Hi all,
I am trying to correct an error that was made with our cvs repository a
while back. We have what we consider to be our "main branch", which has
been tagged with the sticky tag R1-0. Most of the files with that
sticky tag have a working version number in the form 1.1.2.x. However
we have a
[EMAIL PROTECTED] wrote:
> I've had a CVS set up, but an idea crossed my mind. Is there a way to
> make it so that cvs will keep the latest versions of the files in the
> repository (in their working form, not diff form) on the server in a
> folder separate from the repository?
Yes - look at the s
I'm not really answering your question as I have not done any kind of
timing analysis on the various storage methods. However, I have seen
other systems that use the following methods. Based on their
algorithms, one would expect these to be listed in order of decreasing
speed for arbitrary ve
I'm not sure of the speeds, but it's a two-edged sword. Keeping full copies of
everything bloats the database requirements for CVS, making the disk space an
issue. And I couldn't say whether not using the "diff" to create deltas to
keep instead would be faster or slower than checking in a full c
14 matches
Mail list logo
