From: "Ping Yin" <pkufranky@gmail.com>
To: "Avery Pennarun" <apenwarr@gmail.com>
Cc: "Nigel Magnay" <nigel.magnay@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git submodules and commit
Date: Sat, 19 Jul 2008 00:11:54 +0800 [thread overview]
Message-ID: <46dff0320807180911h63999019q5dd56e9341d0fbb6@mail.gmail.com> (raw)
In-Reply-To: <32541b130807160843k25f1d7d3u8bfecd6c1c6eab91@mail.gmail.com>
On Wed, Jul 16, 2008 at 11:43 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
> On 7/16/08, Nigel Magnay <nigel.magnay@gmail.com> wrote:
> If you want to work with me on my new submodule workflow (and I'd
> certainly appreciate it!) then I'd suggest one or more of the
> following starting points:
>
> - Take the recursive push, pull, and update operations described
> above, make them general (ie. not referring to my submodules by name
> :)), and add them as commands in the real git-submodule script. The
> trickiest part here will be figuring out which remote branch to
> push/pull.
See http://article.gmane.org/gmane.comp.version-control.git/69834
([PATCH] Added recurse command to git submodule)
Or search "submodule recursive" in gmane.
The recursive pull,diff,status for submodule is implemented by Imran M
Yousuf. And IIRC, with this patch, you can walk through the submodule
hierarchy to exectute any command.
--
Ping Yin
prev parent reply other threads:[~2008-07-18 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <320075ff0807160331j30e8f832m4de3e3bbe9c26801@mail.gmail.com>
2008-07-16 10:32 ` git submodules and commit Nigel Magnay
2008-07-16 10:47 ` Johannes Sixt
2008-07-16 11:02 ` Nigel Magnay
2008-07-16 11:35 ` Johannes Sixt
2008-07-16 12:11 ` Petr Baudis
2008-07-16 12:48 ` Nigel Magnay
2008-07-16 13:38 ` Johannes Sixt
2008-07-16 14:03 ` Nigel Magnay
2008-07-16 14:17 ` Petr Baudis
2008-07-16 14:31 ` Nigel Magnay
2008-07-16 15:43 ` Avery Pennarun
2008-07-17 9:47 ` Nigel Magnay
2008-07-17 15:12 ` Avery Pennarun
2008-07-18 16:11 ` Ping Yin [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=46dff0320807180911h63999019q5dd56e9341d0fbb6@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=nigel.magnay@gmail.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).