From: Stefan Beller <sbeller@google.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, hvoigt@hvoigt.net,
torvalds@linux-foundation.org, peff@peff.net,
Stefan Beller <sbeller@google.com>
Subject: [PATCH 0/2] submodule pushes be extra careful
Date: Thu, 6 Oct 2016 12:37:23 -0700 [thread overview]
Message-ID: <20161006193725.31553-1-sbeller@google.com> (raw)
This is a reroll of
http://public-inbox.org/git/20161004210359.15266-1-sbeller@google.com/
([PATCHv3 1/2] push: change submodule default to check when submodules exist)
but with a test.
As we only have a heuristic, the test failed initially as these tests don't
have any configuration at all nor do they have the submodule repos in the
superprojects git dir. So I was looking for a cheap way to add a config.
I could have written the config myself via git config, I think it is more
idiomatic to use a submodule command for that. However just getting the
configuration added is not possible with a submodule command, so I made one
in the first patch.
Thanks,
Stefan
Stefan Beller (2):
submodule add: extend force flag to add existing repos
push: change submodule default to check when submodules exist
builtin/push.c | 15 ++++++++++++++-
git-submodule.sh | 10 ++++++++--
t/t5531-deep-submodule-push.sh | 6 +++++-
t/t7400-submodule-basic.sh | 14 ++++++++++++++
4 files changed, 41 insertions(+), 4 deletions(-)
--
2.10.1.353.g1629400
next reply other threads:[~2016-10-06 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 19:37 Stefan Beller [this message]
2016-10-06 19:37 ` [PATCH 1/2] submodule add: extend force flag to add existing repos Stefan Beller
2016-10-06 20:11 ` Junio C Hamano
2016-10-07 12:52 ` Heiko Voigt
2016-10-07 17:25 ` Stefan Beller
2016-10-11 16:36 ` Heiko Voigt
2016-10-06 19:37 ` [PATCHv4 2/2] push: change submodule default to check when submodules exist Stefan Beller
2016-10-06 20:25 ` Junio C Hamano
2016-10-06 21:29 ` Stefan Beller
2016-10-06 23:41 ` [PATCHv5] " 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=20161006193725.31553-1-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=peff@peff.net \
--cc=torvalds@linux-foundation.org \
/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).