From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Jens.Lehmann@web.de, gmane@otterhall.com,
Stefan Beller <sbeller@google.com>
Subject: [PATCH 0/2] WAS: [PATCH] mv: allow moving nested submodules
Date: Mon, 18 Apr 2016 16:41:22 -0700 [thread overview]
Message-ID: <1461022884-30819-1-git-send-email-sbeller@google.com> (raw)
A single patch evolves into a series.
The second patch is essentially a resend with Junios suggestion squashed[1].
That patch alone doesn't quite fix it yet, as we need to make sure the
submodule code respects the ignore_errors flag as instructed by the user.
Patch 1 libifies the used functions from submodule.c and handles the errors
appropriately.
[1] http://thread.gmane.org/gmane.comp.version-control.git/291810/focus=291829
Thanks,
Stefan
Stefan Beller (2):
mv submodule: respect ignore_errors for errors in submodule code
mv: allow moving nested submodules
builtin/mv.c | 32 +++++++++++++++++++++++---------
submodule.c | 33 ++++++++++++++++++++++++---------
submodule.h | 6 ++++--
t/t7001-mv.sh | 16 ++++++++++++++++
4 files changed, 67 insertions(+), 20 deletions(-)
--
2.8.1.211.g24879d1
next reply other threads:[~2016-04-18 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 23:41 Stefan Beller [this message]
2016-04-18 23:41 ` [PATCH 1/2] mv submodule: respect ignore_errors for errors in submodule code Stefan Beller
2016-04-18 23:41 ` [PATCH 2/2] mv: allow moving nested submodules Stefan Beller
2016-04-19 7:13 ` Jacob Keller
2016-04-19 0:01 ` [PATCH 0/2] WAS: [PATCH] " Junio C Hamano
2016-04-19 16:56 ` Stefan Beller
2016-04-19 18:15 ` 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=1461022884-30819-1-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gmane@otterhall.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).