This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [COMMIT] Accept "\r\n" line-endings on all hosts

From: Andreas Schwab <schwab at suse dot de>
To: Eli Zaretskii <eliz at gnu dot org>
Cc: Mark Kettenis <mark dot kettenis at xs4all dot nl>, cagney at gnu dot org,gdb-patches at sources dot redhat dot com
Date: Fri, 15 Oct 2004 01:00:05 +0200
Subject: Re: [COMMIT] Accept "\r\n" line-endings on all hosts
References: <200410141244.i9ECiXMQ008862@elgar.sibelius.xs4all.nl><416E835F.9040702@gnu.org><200410141837.i9EIbJCO000581@elgar.sibelius.xs4all.nl><01c4b231$Blat.v2.2.2$da772700@zahav.net.il>

"Eli Zaretskii" <eliz@gnu.org> writes:

>> Date: Thu, 14 Oct 2004 20:37:19 +0200 (CEST)
>> From: Mark Kettenis <mark.kettenis@xs4all.nl>
>> CC: gdb-patches@sources.redhat.com
>> 
>> 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).

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."

Follow-Ups:
- Re: [COMMIT] Accept "\r\n" line-endings on all hosts
  - From: Eli Zaretskii

References:
- [COMMIT] Accept "\r\n" line-endings on all hosts
  - From: Mark Kettenis
- Re: [COMMIT] Accept "\r\n" line-endings on all hosts
  - From: Andrew Cagney
- Re: [COMMIT] Accept "\r\n" line-endings on all hosts
  - From: Mark Kettenis
- Re: [COMMIT] Accept "\r\n" line-endings on all hosts
  - From: Eli Zaretskii

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]