unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] Changes to emacs/nt/INSTALL
Date: Sat, 18 Jun 2005 12:55:04 +0200	[thread overview]
Message-ID: <u8y180waf.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b050613155277fae555@mail.gmail.com> (message from Juanma Barranquero on Tue, 14 Jun 2005 00:52:06 +0200)

> Date: Tue, 14 Jun 2005 00:52:06 +0200
> From: Juanma Barranquero <lekktu@gmail.com>
> Cc: emacs-devel@gnu.org
> 
> On 6/12/05, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > Anyway, I'm still confused.  Assuming that I checkout a file with -kb,
> > and that file is not recorded as binary in the repository, would
> > commands such as "cvs diff", "cvs annotate", etc. work exactly as when
> > no -kb was ever used on that file?
> 
> cvs diff, annotate, etc. do work as if the files weren't checked out with -kb.

Thanks for the footwork.  I've now removed the warning from
nt/INSTALL.

> > Finally, if "co -kb" indeed has only a local effect, and none of the
> > other commands, like ci, diff, up -j, etc. are affected, it sounds
> > like Windows users should be told to checkout the whole tree with -kb,
> > right?
> 
> Not sure if they should be told to, but at least there is no problem
> if they do: I just checked out a -kb tree and built it with MSVC with
> no problem whatsoever.

I did that as well (but with MinGW).  I will run with this setup for a
while and see if I encounter any problems.

  reply	other threads:[~2005-06-18 10:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Dh4D3-0006WZ-00@savannah.gnu.org>
2005-06-11 16:33 ` [Emacs-diffs] Changes to emacs/nt/INSTALL Juanma Barranquero
2005-06-11 20:20   ` Eli Zaretskii
2005-06-11 21:09     ` Jason Rumney
2005-06-12  9:09       ` Eli Zaretskii
2005-06-12 12:36         ` Jason Rumney
2005-06-13 22:52         ` Juanma Barranquero
2005-06-18 10:55           ` Eli Zaretskii [this message]
2005-06-18 14:27             ` Eli Zaretskii
2005-06-12  2:43     ` Juanma Barranquero

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=u8y180waf.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).