Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>,
	Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] Accept "\r\n" line-endings on all hosts
Date: Thu, 14 Oct 2004 19:09:00 -0000	[thread overview]
Message-ID: <416ECEE0.8010205@gnu.org> (raw)
In-Reply-To: <200410141837.i9EIbJCO000581@elgar.sibelius.xs4all.nl>

>    Date: Thu, 14 Oct 2004 09:47:11 -0400
>    From: Andrew Cagney <cagney@gnu.org>
> 
>    > In the discussion about elimination of the Cygwin and DJGPP xm.h files
>    > we seemed to have reached agreement on this.  Actually this is a real
>    > improvement, since it will allow you to execute scripts copied from a
>    > system using the MS-DOS convention without converting them.
> 
>    Can this be tested?  A one line uuencoded script comes to mind.
> 
> Yup should be doable.  No uuencoding necessary I think.  Unless CVS
> silently changes \r\n into \n.

I suspect, dependant on how the file is created in CVS, that: UNIX ci; 
dos co; dos tweak; dos ci; UNIX co; might do it.

I was actually more worried by human error.  I suspect a few lines of 
tcl that just generate the file are easiest.

Andrew



  reply	other threads:[~2004-10-14 19:09 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 [this message]
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

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=416ECEE0.8010205@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=mec.gnu@mindspring.com \
    /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