From: Heiko Voigt <hvoigt@hvoigt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jens Lehmann <jens.lehmann@web.de>,
Brad King <brad.king@kitware.com>,
Fredrik Gustafsson <iveqy@iveqy.com>
Subject: Re: What's cooking in git.git (Oct 2011, #03; Fri, 7)
Date: Mon, 10 Oct 2011 22:16:29 +0200 [thread overview]
Message-ID: <20111010201629.GB5981@sandbox-rc> (raw)
In-Reply-To: <7vsjn4tukt.fsf@alter.siamese.dyndns.org>
Hi Junio,
sorry for the late reply I was taking some time off from email. Here now
some information on the two topics I am involved with that got stalled:
On Fri, Oct 07, 2011 at 01:28:34PM -0700, Junio C Hamano wrote:
> --------------------------------------------------
> [Stalled]
>
> * hv/submodule-merge-search (2011-08-26) 5 commits
> - submodule: Search for merges only at end of recursive merge
> - allow multiple calls to submodule merge search for the same path
> - submodule: Demonstrate known breakage during recursive merge
The three patches above belong to the merge-search fix topic. I think
they should be good to go.
> - push: Don't push a repository with unpushed submodules
> - push: teach --recurse-submodules the on-demand option
> (this branch is tangled with fg/submodule-auto-push.)
These two belong into the fg/submodule-auto-push topic. It seems they
got mixed into this while dicussing the two topics.
> The second from the bottom one needs to be replaced with a properly
> written commit log message.
I will look into that.
> * fg/submodule-auto-push (2011-09-11) 2 commits
> - submodule.c: make two functions static
> - push: teach --recurse-submodules the on-demand option
> (this branch is tangled with hv/submodule-merge-search.)
>
> What the topic aims to achieve may make sense, but the implementation
> looked somewhat suboptimal.
We will also have a look at the final cleanups we need here. (Fredrik?)
Cheers Heiko
prev parent reply other threads:[~2011-10-10 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 20:28 What's cooking in git.git (Oct 2011, #03; Fri, 7) Junio C Hamano
2011-10-10 20:16 ` Heiko Voigt [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=20111010201629.GB5981@sandbox-rc \
--to=hvoigt@hvoigt.net \
--cc=brad.king@kitware.com \
--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).