unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: "checksum failure after patch" in CVS
Date: Tue, 5 Jul 2005 10:23:33 +0200	[thread overview]
Message-ID: <f7ccd24b050705012328e79e70@mail.gmail.com> (raw)
In-Reply-To: <uacl1q3ha.fsf@gnu.org>

On 7/5/05, Eli Zaretskii <eliz@gnu.org> wrote:

> You are, in effect, saying that Emacs is wrong decoding non-Unix EOLs
> and treating the result as text by hiding the alien EOL sequences from
> the user when it displays the file.  Because if config.bat is a binary
> file, we should have visited it with no-conversion.

No. I'm specifically speaking of CVS. Nothing that I did say bears any
relation with Emacs. I'm talking about what CVS and CVS clients *do*
and *expect* from text and/or binary files.

And, as I said, it is a terminology issue. I'm not questioning that
you and Jason are right. That does not keep me from shooting my foot
every now and then because of the CR/LF "text" files in the
repository.

> It's not evil because storing it as a binary loses some valuable
> features of CVS, like the ability to say "cvs diff", "cvs annotate",
> etc.

That's why I'd like for them to be text with LF. I'm not advocating
having CR/LF files in binary. Heck, I'm not "advocating" anything.
I've already understood why some people has decided to have CR/LF
.BATs in the repository as text files. That I understand what has been
done doesn't preclude me of thinking of it as evil (the fact, not the
people, of course).

> What _is_ evil is the broken manner in which Windows CVS clients
> handle the EOL issue.

That, too. But CVSNT is *the* CVS client for Windows, it is widely
deployed. Even if they fixed that, there'd be still a lot of people
running older copies. So we have something in the repository which is
likely to cause problems to Windows developers and users (at least
those who're going to compile their own Emacs).

> No, config.bat was always stored with DOS EOLs in the Emacs CVS.

Funny, then. It's been changed at other times and I never had the problem.

-- 
                    /L/e/k/t/u

  reply	other threads:[~2005-07-05  8:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 14:41 "checksum failure after patch" in CVS Juanma Barranquero
2005-07-04 14:47 ` Juanma Barranquero
2005-07-04 15:45   ` Jason Rumney
2005-07-04 22:50     ` Eli Zaretskii
2005-07-04 22:34       ` Jason Rumney
2005-07-04 23:08     ` Juanma Barranquero
2005-07-05  4:30       ` Eli Zaretskii
2005-07-05  8:23         ` Juanma Barranquero [this message]
2005-07-05 21:18           ` Eli Zaretskii
2005-07-04 22:47   ` Eli Zaretskii
2005-07-04 22:59     ` 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=f7ccd24b050705012328e79e70@mail.gmail.com \
    --to=lekktu@gmail.com \
    --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).