From: Heiko Voigt <hvoigt@hvoigt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Fredrik Gustafsson <iveqy@iveqy.com>,
Jens Lehmann <jens.lehmann@web.de>
Subject: [PATCH v5 0/3] push: submodule support
Date: Mon, 13 Feb 2012 10:25:41 +0100 [thread overview]
Message-ID: <20120213092541.GA15585@t1405.greatnet.de> (raw)
I have rewritten and cleaned up the recursive submodule on-demand push
patch from Fredrik. Since this involved changing large parts of it I
have taken over the ownership. To pay credit that this is built upon
Fredriks work I have left the signed-off and mentored-by footers the
same. I hope that this is the proper way to handle such cases. If
someone comes up with a better idea I am happy to change things.
Cheers Heiko
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
The fourth iteration of this patch series can be found here:
http://thread.gmane.org/gmane.comp.version-control.git/179731
Heiko Voigt (3):
Teach revision walking machinery to walk multiple times sequencially
Refactor submodule push check to use string list instead of integer
push: teach --recurse-submodules the on-demand option
.gitignore | 1 +
Documentation/git-push.txt | 14 +++-
Documentation/technical/api-revision-walking.txt | 5 +
Makefile | 1 +
builtin/push.c | 7 ++
object.c | 11 +++
object.h | 2 +
revision.c | 5 +
revision.h | 1 +
submodule.c | 70 ++++++++++++++---
submodule.h | 4 +-
t/t0062-revision-walking.sh | 33 ++++++++
t/t5531-deep-submodule-push.sh | 94 ++++++++++++++++++++++
test-revision-walking.c | 66 +++++++++++++++
transport.c | 41 +++++++++-
transport.h | 1 +
16 files changed, 338 insertions(+), 18 deletions(-)
create mode 100755 t/t0062-revision-walking.sh
create mode 100644 test-revision-walking.c
--
1.7.9.114.gead08
next reply other threads:[~2012-02-13 9:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 9:25 Heiko Voigt [this message]
2012-02-13 9:27 ` [PATCH v5 1/3] Teach revision walking machinery to walk multiple times sequencially Heiko Voigt
2012-02-14 1:33 ` Junio C Hamano
2012-03-26 19:32 ` Heiko Voigt
2012-03-26 21:28 ` Junio C Hamano
2012-02-13 9:29 ` [PATCH v5 2/3] Refactor submodule push check to use string list instead of integer Heiko Voigt
2012-02-14 3:28 ` Junio C Hamano
2012-03-26 19:33 ` Heiko Voigt
2012-03-26 19:55 ` Heiko Voigt
2012-03-26 21:29 ` Junio C Hamano
2012-02-13 9:30 ` [PATCH v5 3/3] push: teach --recurse-submodules the on-demand option Heiko Voigt
2012-02-14 3:34 ` Junio C Hamano
2012-02-15 22:28 ` Jens Lehmann
2012-03-26 19:33 ` Heiko Voigt
2012-05-13 14:47 ` [RFC/PATCH] read from 2 filedescriptors simultaneously into one strbuf Heiko Voigt
2012-03-26 21:22 ` [PATCH v5 3/3] push: teach --recurse-submodules the on-demand option Zbigniew Jędrzejewski-Szmek
2012-03-28 15:30 ` Heiko Voigt
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=20120213092541.GA15585@t1405.greatnet.de \
--to=hvoigt@hvoigt.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=iveqy@iveqy.com \
--cc=jens.lehmann@web.de \
/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).