Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Sandiford <rdsandiford@googlemail.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Tom Tromey <tromey@redhat.com>,
	 Fred Cooke <fred.cooke@gmail.com>,
	 Binutils Development <binutils@sourceware.org>,
	 GDB Development <gdb@sourceware.org>
Subject: Re: git conversion status
Date: Tue, 15 Oct 2013 16:57:00 -0000	[thread overview]
Message-ID: <87ppr6lbea.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com> (raw)
In-Reply-To: <alpine.BSF.2.02.1310142206310.2993@arjuna.pair.com> (Hans-Peter	Nilsson's message of "Mon, 14 Oct 2013 22:12:15 -0400 (EDT)")

Hans-Peter Nilsson <hp@bitrange.com> writes:
> On Mon, 14 Oct 2013, Tom Tromey wrote:
>> Fred> 'git clone URL' will produce a directory called "src" which
>> Fred> is utterly meaningless on any developer's machine.
>>
>> I chose it because the existing repository is named "src".
>
> Counter-argument:
> I *prefer* src, exactly for that reason; "scripts expect that".
>
> If you-all want binutils+gdb (or some other combination of their
> names), I can live with that, but not another generic name just
> because someone offers the opinion that "src is utterly
> meaningless".  It's not: it's the default name of the check-out
> directory of sourceware top-level...

+1 FWIW.  I don't mind what the thing's called, but renaming from
src feels like make-work.  And I disagree that "src is utterly
meaningless on any developer's machine".  It actually fits quite
nicely in a:

  binutils/
    src/
    mips64-linux-gnu/
    x86_64-linux-gnu/
    ...

layout.

I usually find I end up specifying a repo name explicitly
("git clone URL dir") with other projects anyway.

Richard


  parent reply	other threads:[~2013-10-15 16:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 17:01 Tom Tromey
2013-10-14 17:07 ` Fred Cooke
2013-10-14 17:45   ` Tom Tromey
2013-10-14 19:01     ` Jan-Benedict Glaw
2013-10-14 19:07     ` Jan Kratochvil
2013-10-14 20:02     ` Andreas Schwab
2013-10-14 20:08       ` Tom Tromey
2013-10-14 20:11       ` Fred Cooke
2013-10-14 23:08     ` Joseph S. Myers
2013-10-15 13:18       ` Tom Tromey
2013-10-15 13:25         ` Fred Cooke
2013-10-15 15:09         ` Joseph S. Myers
2013-10-15 22:35         ` Hans-Peter Nilsson
2013-10-15  2:12     ` Hans-Peter Nilsson
2013-10-15  7:21       ` Andreas Schwab
2013-10-15  8:03       ` Tim Sander
2013-10-15 16:57       ` Richard Sandiford [this message]
2013-10-15 17:52     ` Stan Shebs
2013-10-15  9:56 ` Joel Brobecker
2013-10-15 13:19   ` 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=87ppr6lbea.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com \
    --to=rdsandiford@googlemail.com \
    --cc=binutils@sourceware.org \
    --cc=fred.cooke@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=hp@bitrange.com \
    --cc=tromey@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