From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark.kettenis@xs4all.nl, cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] Accept "\r\n" line-endings on all hosts
Date: Fri, 15 Oct 2004 13:48:00 -0000 [thread overview]
Message-ID: <jesm8gnlw1.fsf@sykes.suse.de> (raw)
In-Reply-To: <01c4b2b4$Blat.v2.2.2$2ec2eb00@zahav.net.il> (Eli Zaretskii's message of "Fri, 15 Oct 2004 14:39:38 +0200")
"Eli Zaretskii" <eliz@gnu.org> writes:
>> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, cagney@gnu.org,
>> gdb-patches@sources.redhat.com
>> From: Andreas Schwab <schwab@suse.de>
>> Date: Fri, 15 Oct 2004 01:00:05 +0200
>>
>> >> Yup should be doable. No uuencoding necessary I think. Unless CVS
>> >> silently changes \r\n into \n.
>> >
>> > Some Windows CVS clients do that.
>>
>> Unless you mark the file as binary (-kb).
>
> And lose important features like diffs, per-line annotations, etc.
> No, thanks.
For a single small file just for testing purpose that should not pose much
problem. Otherwise I agree.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-10-15 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 12:44 Mark Kettenis
2004-10-14 13:47 ` Andrew Cagney
2004-10-14 18:37 ` Mark Kettenis
2004-10-14 19:09 ` Andrew Cagney
2004-10-14 19:48 ` Mark Kettenis
2004-10-14 19:59 ` Andrew Cagney
2004-10-15 2:16 ` Michael Chastain
2004-10-14 21:11 ` Eli Zaretskii
2004-10-14 23:03 ` Andreas Schwab
2004-10-15 12:43 ` Eli Zaretskii
2004-10-15 13:48 ` Andreas Schwab [this message]
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=jesm8gnlw1.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox