From: Max Krasnyansky <maxk@qualcomm.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: <git@vger.kernel.org>
Subject: Re: Auto update submodules after merge and reset
Date: Mon, 5 Dec 2011 17:06:20 -0800 [thread overview]
Message-ID: <4EDD6A8C.40008@qualcomm.com> (raw)
In-Reply-To: <4ED5E9D2.4060503@web.de>
Hi Jens,
On 11/30/2011 12:31 AM, Jens Lehmann wrote:
> I'm working on a patch series to teach Git to optionally update the
> submodules work trees on checkout, reset merge and so on, but I'm not
> there yet.
> [SNIP]
Sorry for not replying right away.
Everything you suggested sounds great. We're on the same page (config
option, etc).
How far along are you? Do you have a tree I could pull from to play with
things?
I could help with testing, bug fixes and/or implementing parts of it.
Let me know.
For now I implemented automatic submodules update using 'post-merge'
hook. But obviously it does
not handle reset and things. I'm thinking of adding 'post-reset' and
'pre-merge' that would be useful
for this and maybe other things.
Thanx
Max
next prev parent reply other threads:[~2011-12-06 1:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 0:55 Auto update submodules after merge and reset Max Krasnyansky
2011-11-30 8:31 ` Jens Lehmann
2011-12-06 1:06 ` Max Krasnyansky [this message]
2011-12-06 21:32 ` Jens Lehmann
2011-12-07 9:07 ` Andreas T.Auer
2011-12-07 22:23 ` Jens Lehmann
2011-12-08 9:13 ` andreas.t.auer_gtml_37453
2011-12-09 23:57 ` Phil Hord
2011-12-10 1:41 ` Andreas T.Auer
2011-12-11 14:43 ` Phil Hord
2011-12-11 21:15 ` Andreas T.Auer
2011-12-12 22:39 ` Jens Lehmann
2011-12-12 23:43 ` Phil Hord
2011-12-13 7:52 ` Jens Lehmann
2011-12-13 9:45 ` Andreas T.Auer
2011-12-13 21:44 ` Jens Lehmann
2011-12-13 23:05 ` Andreas T.Auer
2011-12-14 15:16 ` Marc Branchaud
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=4EDD6A8C.40008@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.