From: Jens Lehmann <Jens.Lehmann@web.de>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Johannes Sixt <j6t@kdbg.org>
Subject: Re: [PATCH v4 0/6] submodule: drop the top-level requirement
Date: Mon, 17 Jun 2013 22:41:51 +0200 [thread overview]
Message-ID: <51BF748F.7070708@web.de> (raw)
In-Reply-To: <cover.1371391740.git.john@keeping.me.uk>
Am 16.06.2013 16:18, schrieb John Keeping:
> 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.
Thanks for working on this! This series is looking good to me.
> 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
>
prev parent reply other threads:[~2013-06-17 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 14:18 [PATCH v4 0/6] submodule: drop the top-level requirement John Keeping
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 ` Jens Lehmann [this message]
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=51BF748F.7070708@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=john@keeping.me.uk \
--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.