From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: ^m's in testsuite/gdb.disasm
Date: Wed, 31 Oct 2007 20:22:00 -0000 [thread overview]
Message-ID: <20071031202211.GA28571@caradoc.them.org> (raw)
In-Reply-To: <u7il3qbpw.fsf@gnu.org>
On Wed, Oct 31, 2007 at 10:18:51PM +0200, Eli Zaretskii wrote:
> As for other files, IMO they should only have CR-LF if the development
> tools or programs that use them require that. I don't think *.s
> assembly source files qualify; chances are they were simply committed
> from a Windows machine...
I agree; I suspect it's just an accident.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-31 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 19:21 Doug Evans
2007-10-31 20:19 ` Eli Zaretskii
2007-10-31 20:22 ` Daniel Jacobowitz [this message]
2007-10-31 20:36 ` frank.theinen
2007-11-01 23:45 ` Douglas Evans
2007-11-02 0:38 ` Daniel Jacobowitz
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=20071031202211.GA28571@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.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