From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Where is patch? - problems with patch.exe on w32
Date: Fri, 16 Dec 2005 09:38:23 +0200 [thread overview]
Message-ID: <uvexppk40.fsf@gnu.org> (raw)
In-Reply-To: <43A1CFD4.2010201@student.lu.se> (message from Lennart Borgman on Thu, 15 Dec 2005 21:19:32 +0100)
> Date: Thu, 15 Dec 2005 21:19:32 +0100
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> CC: emacs-devel@gnu.org
>
> I use the same command for update and initial checkout. Do you then add
> -kb to the command described on Emacs home page at Savannah?
Both "co" and "up" accept the -kb option. So just add -kb to these
two commands as described on the savannah page.
> Since this procedure is not the standard procedure as far as I
> understand I wonder if there are any more problems with doing so? What
> about check ins? What about those part in the emacs/nt subdirectory?
No problems at all, except that "cvs up" cannot patch files (because
they are treated as binary), so it downloads the whole files
downstream, which takes longer, especially with large files (such as
ChangeLog). Unless your connection is slow, this shouldn't matter
much, though.
Anyway, this has nothing to do with Patch; as I wrote patching Emacs
works even if you don't checkout with -kb. (And I think we are way
off topic on this list, anyway.)
next prev parent reply other threads:[~2005-12-16 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43A064AD.4050604@student.lu.se>
[not found] ` <20051214192858.GM2399@calimero.vinschen.de>
[not found] ` <43A07425.70205@student.lu.se>
2005-12-14 20:04 ` Where is patch? - problems with patch.exe on w32 Lennart Borgman
2005-12-15 4:26 ` Eli Zaretskii
2005-12-15 8:19 ` Lennart Borgman
2005-12-15 19:26 ` Eli Zaretskii
2005-12-15 20:19 ` Lennart Borgman
2005-12-16 7:38 ` Eli Zaretskii [this message]
[not found] ` <dnpsv8$o2r$1@sea.gmane.org>
2005-12-14 20:28 ` Where is patch? Lennart Borgman
2005-12-15 4:29 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uvexppk40.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).