From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Jens.Lehmann@web.de,
Stefan Beller <sbeller@google.com>,
Per Cederqvist <cederp@opera.com>
Subject: [PATCH 00/10] submodule output patches
Date: Fri, 29 Apr 2016 17:40:35 -0700 [thread overview]
Message-ID: <1461976845-18228-1-git-send-email-sbeller@google.com> (raw)
Patch 1 was send outside of a series already.
Patch 2 and 3 are preparatory things for the submodule groups stuff
patches 4-9 are making the output of the submodule command consistent
(similar to patch 3, but I do not foresee a need for it yet)
Patch 10 is a controversial thing I'd assume as it breaks existing users.
We should take it for the next major release (i.e. 3.0)
I just want to put it out here now.
Thanks,
Stefan
Stefan Beller (10):
submodule deinit test: fix broken && chain in subshell
submodule deinit: lose requirement for giving '.'
submodule init: redirect stdout to stderr
shell helpers usage: always send help to stderr
submodule add: send messages to stderr
submodule deinit: send messages to stderr
submodule foreach: send messages to stderr
submodule update: send messages to stderr
submodule sync: send messages to stderr
submodule deinit: complain when given a file instead of a submodule
builtin/submodule--helper.c | 9 +++++----
git-sh-setup.sh | 2 +-
git-submodule.sh | 21 ++++++++-------------
t/t7400-submodule-basic.sh | 38 +++++++++++++++++++++++++-------------
t/t7403-submodule-sync.sh | 4 ++--
t/t7406-submodule-update.sh | 23 ++++++++++++++++-------
t/t7407-submodule-foreach.sh | 35 ++++++++++++++++++++++-------------
7 files changed, 79 insertions(+), 53 deletions(-)
--
2.8.0.32.g71f8beb.dirty
next reply other threads:[~2016-04-30 0:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 0:40 Stefan Beller [this message]
2016-04-30 0:40 ` [PATCH 01/10] submodule deinit test: fix broken && chain in subshell Stefan Beller
2016-04-30 0:40 ` [PATCH 02/10] submodule deinit: lose requirement for giving '.' Stefan Beller
2016-04-30 0:40 ` [PATCH 03/10] submodule init: redirect stdout to stderr Stefan Beller
2016-04-30 0:40 ` [PATCH 04/10] shell helpers usage: always send help " Stefan Beller
2016-05-02 23:28 ` Junio C Hamano
2016-05-02 23:44 ` Stefan Beller
2016-05-03 0:45 ` Junio C Hamano
2016-05-03 1:17 ` Junio C Hamano
2016-04-30 0:40 ` [PATCH 05/10] submodule add: send messages " Stefan Beller
2016-05-02 23:26 ` Junio C Hamano
2016-04-30 0:40 ` [PATCH 06/10] submodule deinit: " Stefan Beller
2016-05-02 23:28 ` Junio C Hamano
2016-04-30 0:40 ` [PATCH 07/10] submodule foreach: " Stefan Beller
2016-04-30 0:40 ` [PATCH 08/10] submodule update: " Stefan Beller
2016-04-30 0:40 ` [PATCH 09/10] submodule sync: " Stefan Beller
2016-04-30 0:40 ` [PATCH 10/10] submodule deinit: complain when given a file instead of a submodule Stefan Beller
2016-05-02 8:26 ` Per Cederqvist
2016-05-02 16:21 ` Stefan Beller
2016-05-02 17:00 ` Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1461976845-18228-1-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=cederp@opera.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).