From: Jens Lehmann <Jens.Lehmann@web.de>
To: git@vger.kernel.org
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
gitster@pobox.com, hvoigt@hvoigt.net
Subject: Re: [PATCH v4 0/2] push limitations
Date: Sun, 14 Aug 2011 19:29:49 +0200 [thread overview]
Message-ID: <4E48060D.9010106@web.de> (raw)
In-Reply-To: <1313312262-2460-1-git-send-email-iveqy@iveqy.com>
Please ignore this series, it slipped through by accident.
Am 14.08.2011 10:57, schrieb Fredrik Gustafsson:
> The first iteration of this patch series can be found here:
> http://thread.gmane.org/gmane.comp.version-control.git/176328/focus=176327
>
> The second iteration of this patch series can be found here:
> http://thread.gmane.org/gmane.comp.version-control.git/177992
>
> The third iteration of this patch series can be found here:
> http://thread.gmane.org/gmane.comp.version-control.git/179037/focus=179048
>
>
> Fredrik Gustafsson (2):
> rev-parse: add option --is-well-formed-git-dir [path]
> push: Don't push a repository with unpushed submodules
>
> Documentation/git-push.txt | 6 ++
> Documentation/git-rev-parse.txt | 4 ++
> builtin/push.c | 17 ++++++
> builtin/rev-parse.c | 8 +++
> cache.h | 1 +
> combine-diff.c | 2 +-
> setup.c | 7 +++
> submodule.c | 108 +++++++++++++++++++++++++++++++++++++++
> submodule.h | 1 +
> t/t5531-deep-submodule-push.sh | 94 ++++++++++++++++++++++++++++++++++
> t/t7400-submodule-basic.sh | 4 +-
> t/t7403-submodule-sync.sh | 5 +-
> t/t7407-submodule-foreach.sh | 97 ++++++++++++++++++-----------------
> transport.c | 9 +++
> transport.h | 1 +
> 15 files changed, 312 insertions(+), 52 deletions(-)
>
prev parent reply other threads:[~2011-08-14 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 8:57 [PATCH v4 0/2] push limitations Fredrik Gustafsson
2011-08-14 8:57 ` [PATCH v4 2/2] push: Don't push a repository with unpushed submodules Fredrik Gustafsson
2011-08-14 17:29 ` 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=4E48060D.9010106@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=iveqy@iveqy.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).