From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [commit/obv] Remove trailing space in gdbarch.sh.
Date: Wed, 12 Dec 2012 15:46:00 -0000 [thread overview]
Message-ID: <874njr9sup.fsf@fleche.redhat.com> (raw)
In-Reply-To: <50C8A3CD.3000608@redhat.com> (Pedro Alves's message of "Wed, 12 Dec 2012 15:33:33 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> "read" trims leading and trailing whitespace by default (on bash
Pedro> at least). We can make it not do that by setting the IFS
Pedro> variable to empty, like in the patch below. This should make it
Pedro> so that all shells behave the same here (tried bash and dash),
Pedro> which I think would be good.
Pedro> WDYT?
Seems sensible.
I often wish we could replace gdbarch.sh with something nicer.
Tom
next prev parent reply other threads:[~2012-12-12 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 13:56 Joel Brobecker
2012-12-12 15:33 ` Pedro Alves
2012-12-12 15:46 ` Tom Tromey [this message]
2012-12-13 5:47 ` Joel Brobecker
2012-12-13 10:32 ` Pedro Alves
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=874njr9sup.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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