unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: Francis Litterio <flitterio@gmail.com>, emacs-devel@gnu.org
Subject: Re: Bootstrap fails on Win32
Date: Thu, 11 Sep 2008 18:20:12 +0200	[thread overview]
Message-ID: <jehc8m1woz.fsf@sykes.suse.de> (raw)
In-Reply-To: <f7ccd24b0809110843y333d4284nacc0488be5eb6b90@mail.gmail.com> (Juanma Barranquero's message of "Thu, 11 Sep 2008 17:43:41 +0200")

"Juanma Barranquero" <lekktu@gmail.com> writes:

> But IIRC, when you commit changes to the CVS, -kb files are sent
> entirely, while normal non-kb text files are patched (only differences
> are sent). That makes a difference for big files like ChangeLogs.

It's the other way round: patches are received (or not) when updating.
When committing (or diffing) the whole contents are always sent, since
CVS does not have the concept of pristine sources, so it cannot compute
the changes locally.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."




  reply	other threads:[~2008-09-11 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09  7:43 Bootstrap fails on Win32 B. Anyos
2008-09-09 14:31 ` Francis Litterio
2008-09-11  8:14   ` B. Anyos
2008-09-11  8:22     ` Jason Rumney
2008-09-11 10:00       ` B. Anyos
2008-09-11 12:21         ` Juanma Barranquero
2008-09-11 14:31           ` Francis Litterio
2008-09-11 15:43             ` Juanma Barranquero
2008-09-11 16:20               ` Andreas Schwab [this message]
2008-09-11 19:49                 ` Juanma Barranquero
2008-09-11 20:46               ` Stefan Monnier

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=jehc8m1woz.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=emacs-devel@gnu.org \
    --cc=flitterio@gmail.com \
    --cc=lekktu@gmail.com \
    /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).