From: Bill Zaumen <bill.zaumen+git@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: Possible submodule or submodule documentation issue
Date: Sun, 01 Jan 2012 19:53:33 -0800 [thread overview]
Message-ID: <1325476413.1718.20.camel@yos> (raw)
In-Reply-To: <4F00780C.7090801@web.de>
On Sun, 2012-01-01 at 16:13 +0100, Jens Lehmann wrote:
> Am 29.12.2011 03:50, schrieb Bill Zaumen:
> > So what about clarifying
> the docs: ...
Clarifying the docs is a good solution given that a possibly large
number of existing repositories are dependent on the current behavior.
One way of explaining it is to say that "git first appends a
'/' to the superproject's origin URL if that URL does not already
end in a '/'. Relative URLs for submodules' origin repository are
resolved relative to this modified URL." Then the reader can simply
apply the normal URL rules.
I think either is OK - it's simply a judgment call as to which
explanation is easiest for a typical git user to understand.
next prev parent reply other threads:[~2012-01-02 3:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 19:24 Possible submodule or submodule documentation issue Bill Zaumen
2011-12-28 19:47 ` Jens Lehmann
2011-12-29 2:50 ` Bill Zaumen
2012-01-01 15:13 ` Jens Lehmann
2012-01-02 3:53 ` Bill Zaumen [this message]
2012-01-03 20:48 ` Junio C Hamano
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=1325476413.1718.20.camel@yos \
--to=bill.zaumen+git@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.