From: Michael Chastain <mec.gnu@mindspring.com>
To: kettenis@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Testcase for \r\n in command files
Date: Fri, 15 Oct 2004 02:20:00 -0000 [thread overview]
Message-ID: <416F33E8.nail3XL3128QH@mindspring.com> (raw)
In-Reply-To: <200410141856.i9EIuTu6000741@elgar.sibelius.xs4all.nl>
Mark Kettenis <kettenis@gnu.org> wrote:
set scriptfile ${srcdir}/${subdir}/crlf.gdb
I think the "tcl create file" version is safer, although maybe I'm
just a worry-wart about source control systems and line endings.
Michael
prev parent reply other threads:[~2004-10-15 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 18:56 Mark Kettenis
2004-10-15 2:20 ` Michael Chastain [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=416F33E8.nail3XL3128QH@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox