Hi,
But can patch be run in such a way that it generates conflict markers
instead of .rej files? This would be very useful at times. Or is diff3 the
go here instead?
cheers,
matt
-Original Message-
Date: Tue, 7 Jan 2003 17:03:15 -0500
From: Eric Siegerman [EMAIL PROTECTED]
To: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
Subject: Re: How is a patch applied to CVS?
Message-ID: [EMAIL PROTECTED]
In-Reply-To:
[EMAIL PROTECTED];
from[EMAIL PROTECTED] on Mon, Jan 06, 2003 at 08:23:52PM -0500
References:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Precedence: list
Message: 9
On Mon, Jan 06, 2003 at 08:23:52PM -0500, Mazza, Glen R., ,CPMS wrote:
How is a patch file committed into CVS to update
the most recent version?
In several steps:
- Apply the patch to a checked-out working directory
- Resolve any conflicts (i.e. .rej files)
- Compile and test
- cvs commit
CVS itself can't digest arbitrary patch files.
--
| | /\
|-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Just Say No to the faceless cannonfodder stereotype.
- http://www.ainurin.net/ (an Orc site)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, 8 January 2003 14:44
To: [EMAIL PROTECTED]
Subject: Info-cvs Digest, Vol 2, Issue 11
Send Info-cvs mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
http://mail.gnu.org/mailman/listinfo/info-cvs
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of Info-cvs digest...
Today's Topics:
1. RE: cvs hangs while reporting 'version' (SOLVED) (Harig, Mark A.)
2. Docs for cvs 1.11.4 (Douglas Finkle)
3. Re: How is a patch applied to CVS? (Kaz Kylheku)
4. FW: CVS Multiple checkouts prevent.. (Mariappan Muthiah)
5. Re: How is a patch applied to CVS? (Riechers, Matthew W)
6. Re: CVS and multiple platforms - version conflicts,
featuresavailable
etc.
7. Re: CVS and multiple platforms - version conflicts, features
available (Larry Jones)
8. Re: CVS and multiple platforms - version conflicts, features
available etc. (ADFH)
9. Re: How is a patch applied to CVS? (Eric Siegerman)
--
Date: Tue, 7 Jan 2003 14:11:01 -0500
From: Harig, Mark A. [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: cvs hangs while reporting 'version' (SOLVED)
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain;
charset=iso-8859-1
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: list
Message: 1
-Original Message-
From: Larry Jones [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 04, 2003 5:27 PM
To: Harig, Mark A.
Cc: [EMAIL PROTECTED]
Subject: Re: cvs hangs while reporting 'version'
=20
=20
Harig, Mark A. writes:
=20
The above is NOT a typo. After 'read(5,', the output hangs with the
cursor
following the '5,'. I have left this run for nearly thirty=20
minutes to
see
if there was a timeout condition, before using 'Ctrl-C' to halt the
command.
=20
Try upgrading to the recently-released CVS 1.11.4.
=20
-Larry Jones
=20
Thanks for the suggestion. I upgraded my CVS client to 1.11.4. cvs
still
hangs, but at a different place -- during a call to wait():
$ export CVS_RSH=3D/usr/bin/ssh
$ strace cvs -t -f -dIP addr:/path/to/cvs/repos version
(much text omitted)
write(4, UseUnchanged\n, 13) =3D 13
write(4, Global_option -t\nversion\n, 25) =3D 25
read(5, M , 4096) =3D 2
read(5, Concurrent Versions System (CVS)..., 4096) =3D 58
write(1, Server: Concurrent Versions Syst..., 66Server: Concurrent
Versions System (CVS) 1.11.1p1 (client/server)
) =3D 66
read(5, ok\n, 4096) =3D 3
fstat64(4, {st_mode=3DS_IFIFO|0600, st_size=3D0, ...}) =3D 0
close(4)=3D 0
munmap(0x40018000, 4096)=3D 0
fstat64(5, {st_mode=3DS_IFIFO|0600, st_size=3D0, ...}) =3D 0
close(5)=3D 0
munmap(0x40019000, 4096)=3D 0
wait4(7090,=20
Because my ssh connection has been working seemlessly between
the client and server machines, I did not suspect that it
could be the cause of the problem. Nevertheless, I checked
the versions of openssh that I was running on the client
and the server. Because they were different, I upgraded
the version I am running on the client machine to match
the version that I am running on the server machine.
This solved the problem. cvs now works regardless of
whether I use cvs 1.11.4 or cvs 1.11.1p1 as the client.
For future reference to anyone else who might have this
problem, I was running