From: John Keeping <john@keeping.me.uk>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Jens Lehmann <Jens.Lehmann@web.de>, Johannes Sixt <j6t@kdbg.org>,
John Keeping <john@keeping.me.uk>
Subject: [PATCH v4 0/6] submodule: drop the top-level requirement
Date: Sun, 16 Jun 2013 15:18:12 +0100 [thread overview]
Message-ID: <cover.1371391740.git.john@keeping.me.uk> (raw)
Changes since v3:
* There are four new patches, three of which are style fixes for
existing tests and one fixes an existing error message to return a
more accurate path when recursing.
* You now cannot run "git submodule add <relative URL>" from a
subdirectory. Because the interpretation of the URL changes depending
on whether or not remote.origin.url is configured, I have decided to
just ban this for now. If someone comes up with a sensible way to
handle this then we can lift this restriction later.
* The "path" variable exported in "submodule foreach" now uses the
relative path and matches the "sm_path" variable.
* I audited the code again and fixed a few more cases that weren't
printing relative paths (notably "submodule init" and "submodule
foreach").
* More tests.
John Keeping (6):
t7401: make indentation consistent
t7403: modernize style
t7403: add missing && chaining
submodule: show full path in error message
rev-parse: add --prefix option
submodule: drop the top-level requirement
Documentation/git-rev-parse.txt | 16 ++
builtin/rev-parse.c | 24 ++-
git-submodule.sh | 135 ++++++++++----
t/t1513-rev-parse-prefix.sh | 96 ++++++++++
t/t7400-submodule-basic.sh | 80 +++++++++
t/t7401-submodule-summary.sh | 116 +++++++-----
t/t7403-submodule-sync.sh | 388 ++++++++++++++++++++++++++--------------
t/t7406-submodule-update.sh | 15 ++
t/t7407-submodule-foreach.sh | 16 ++
9 files changed, 673 insertions(+), 213 deletions(-)
create mode 100755 t/t1513-rev-parse-prefix.sh
--
1.8.3.779.g691e267
next reply other threads:[~2013-06-16 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 14:18 John Keeping [this message]
2013-06-16 14:18 ` [PATCH v4 1/6] t7401: make indentation consistent John Keeping
2013-06-16 14:18 ` [PATCH v4 2/6] t7403: modernize style John Keeping
2013-06-16 14:18 ` [PATCH v4 3/6] t7403: add missing && chaining John Keeping
2013-06-16 14:18 ` [PATCH v4 4/6] submodule: show full path in error message John Keeping
2013-06-16 14:18 ` [PATCH v4 5/6] rev-parse: add --prefix option John Keeping
2013-06-16 14:18 ` [PATCH v4 6/6] submodule: drop the top-level requirement John Keeping
2013-06-17 20:41 ` [PATCH v4 0/6] " 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=cover.1371391740.git.john@keeping.me.uk \
--to=john@keeping.me.uk \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jrnieder@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 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.