Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patchv3 12/11] New options {relative,basename}-with-system-absolute
Date: Fri, 01 Feb 2013 03:41:00 -0000	[thread overview]
Message-ID: <CADPb22SwcNmbC2NZ0p8--=62StKGpFxRaa0-YN3EkLAvw19JBw@mail.gmail.com> (raw)
In-Reply-To: <83lib9chfb.fsf@gnu.org>

On Thu, Jan 31, 2013 at 10:54 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 31 Jan 2013 10:07:09 -0800
>> From: Doug Evans <dje@google.com>
>> Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches <gdb-patches@sourceware.org>
>>
>> On Wed, Jan 30, 2013 at 7:48 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> >> Date: Wed, 30 Jan 2013 13:48:05 -0800
>> >> From: Doug Evans <dje@google.com>
>> >> Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches <gdb-patches@sourceware.org>
>> >>
>> >> The nice thing about {relative,basename}-with-system-absolute is that
>> >> they are clear.
>> >
>> > They aren't to me.  They might be clear _after_ you know what they
>> > mean, exactly.  But then so would be every shorthand of them.
>>
>> So then why not reduce them even more?
>
> That could work, but hard to tell without seeing specific suggestions.

Apologies.  My point was that at some point things become too terse.
Names aren't just mnemonics to trigger memory - ideally they shouldn't
have to trigger any memory as the name is already clear.

What about basename-with-system-absolute is not clearer than basename-absolute?


  reply	other threads:[~2013-02-01  3:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 22:10 [patchv2 " Jan Kratochvil
2013-01-30  7:48 ` [patchv3 " Jan Kratochvil
2013-01-30 17:15   ` Eli Zaretskii
2013-01-30 18:30     ` Eli Zaretskii
2013-01-30 18:53       ` Jan Kratochvil
2013-01-30 20:11         ` Eli Zaretskii
2013-01-30 21:48           ` Doug Evans
2013-01-31  3:49             ` Eli Zaretskii
2013-01-31 18:07               ` Doug Evans
2013-01-31 18:54                 ` Eli Zaretskii
2013-02-01  3:41                   ` Doug Evans [this message]
2013-02-01  8:09                     ` Eli Zaretskii
2013-02-02 18:12     ` Jan Kratochvil
2013-02-01 20:59   ` Tom Tromey

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='CADPb22SwcNmbC2NZ0p8--=62StKGpFxRaa0-YN3EkLAvw19JBw@mail.gmail.com' \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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