From: Junio C Hamano <gitster@pobox.com>
To: Jon Seymour <jon.seymour@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] submodule: fix handling of supermodules with relative origin URLs
Date: Sat, 19 May 2012 22:16:44 -0700 [thread overview]
Message-ID: <7v4nrbbfer.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAH3AnrrqiXqdHHGZPyOPJ3Zend5JrQX0rKV+pz_mjs3SDjv9DA@mail.gmail.com> (Jon Seymour's message of "Sun, 20 May 2012 08:51:08 +1000")
Jon Seymour <jon.seymour@gmail.com> writes:
> On Sun, May 20, 2012 at 4:56 AM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
>> Am 19.05.2012 06:40, schrieb Jon Seymour:
>>
>> Just a small nit: I'd prefer to replace the 4 occurrences of the term
>> "supermodule" with "superproject".
>
> Sure. I can't argue with precedent, of course, but I guess I was
> favouring the consistency in the suffixes used with sub and super.
We fairly consistently say (even outside the documentation---for example,
listen to the TechTalk Linus gave in May 2007) "superproject" and never
"supermodule". You can tell people who were not paying attention when
they say "supermodule" ;-).
next prev parent reply other threads:[~2012-05-20 5:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-19 4:40 [PATCH 1/2] submodule: add tests for add,sync,init in presence of relative super origin URL Jon Seymour
2012-05-19 4:40 ` [PATCH 2/2] submodule: fix handling of supermodules with relative origin URLs Jon Seymour
2012-05-19 18:56 ` Jens Lehmann
2012-05-19 22:51 ` Jon Seymour
2012-05-19 23:10 ` Jon Seymour
2012-05-19 23:45 ` Jon Seymour
2012-05-20 0:34 ` Jens Lehmann
2012-05-20 1:25 ` Jon Seymour
2012-05-20 5:16 ` Junio C Hamano [this message]
2012-05-20 13:28 ` [PATCH] Consistently use "superproject" instead of "supermodule" Jens Lehmann
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=7v4nrbbfer.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=jon.seymour@gmail.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;
as well as URLs for NNTP newsgroup(s).