From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Oct 2011, #07; Wed, 19)
Date: Fri, 21 Oct 2011 15:47:12 +0200 [thread overview]
Message-ID: <20111021134712.GA4895@goldbirke> (raw)
In-Reply-To: <7vk480bq5q.fsf@alter.siamese.dyndns.org>
Hi,
On Wed, Oct 19, 2011 at 02:57:37PM -0700, Junio C Hamano wrote:
> * sg/complete-refs (2011-10-15) 10 commits
> - completion: remove broken dead code from __git_heads() and __git_tags()
> - completion: fast initial completion for config 'remote.*.fetch' value
> - completion: improve ls-remote output filtering in __git_refs_remotes()
> - completion: query only refs/heads/ in __git_refs_remotes()
> - completion: support full refs from remote repositories
> - completion: improve ls-remote output filtering in __git_refs()
> - completion: make refs completion consistent for local and remote repos
> - completion: optimize refs completion
> - completion: document __gitcomp()
> - Merge branches 'tm/completion-push-set-upstream', 'tm/completion-commit-fixup-squash' and 'sg/completion' into HEAD
I think an octopus merge is unnecessary there, because
tm/completion-push-set-upstream is an independent change, and
sg/completion builds on top of tm/completion-commit-fixup-squash. So
you could just merge sg/completion into HEAD.
Best,
Gábor
prev parent reply other threads:[~2011-10-21 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 21:57 What's cooking in git.git (Oct 2011, #07; Wed, 19) Junio C Hamano
2011-10-21 13:47 ` SZEDER Gábor [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=20111021134712.GA4895@goldbirke \
--to=szeder@ira.uka.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).