all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Timur Aydin <ta@taydin.org>
Subject: Re: cvs emacs build fails on Windows XP
Date: Sat, 28 Jun 2003 17:12:24 +0300	[thread overview]
Message-ID: <m3wuf6guk7.fsf@bonsai.taydin.org> (raw)
In-Reply-To: un0g29y8e.fsf@jasonrumney.net

jasonr (Jason Rumney) @  f2s.com writes:

>> I had to manually change the line-endings (I guess this was due to
>> fetching the source from cvs).
>
> That is neccesary in the nt and leim/CXTERM subdirectories if you use
> a DOS/Windows CVS client that changes the line-ends as it checks
> out. Recent versions of WinCVS and any version of Cygwin CVS can work
> in a mode where they do not change line-ends.

cvs does change line ending according to the underlying platform. This
is by design. A properly added file will be stored on the cvs server
with LF line endings. When checking out, the file will be converted to
have CR/LF line endings under windows, LF line endings under unix (no
change) and LF/CR line endings uder MAC. Properly adding a text file
means adding it while it has the correct line endings for the
underlying platform.

It seems the nt related files and the leim dictionary files have not
been added to the repository properly. They probably have been added
to the cvs repository under linux, while having CR/LF line endings, or
something like that.

-- 
Timur Aydin

  reply	other threads:[~2003-06-28 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28 11:59 cvs emacs build fails on Windows XP Martin Stemplinger
2003-06-28 12:34 ` Jason Rumney
2003-06-28 14:12   ` Timur Aydin [this message]
2003-06-28 14:21     ` Jason Rumney
2003-06-29  3:24     ` Eli Zaretskii
     [not found]     ` <mailman.8828.1056857204.21513.help-gnu-emacs@gnu.org>
2003-07-01 11:00       ` Bart Oldeman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3wuf6guk7.fsf@bonsai.taydin.org \
    --to=ta@taydin.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.