From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Lee Marlow <lee.marlow@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] bash completion: Add completion for 'git help'
Date: Fri, 25 Jul 2008 14:02:15 -0700 [thread overview]
Message-ID: <7v1w1hsmnc.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080725204051.GB23202@spearce.org> (Shawn O. Pearce's message of "Fri, 25 Jul 2008 15:40:51 -0500")
Thanks for an Ack, but personally I do not think the completion of "all
commands" is worth it.
I've been busy with day-job for the past few days, and haven't had chance
to push things out today, but FYI here is what I already have on 'master'
privately, relative to what have already been pushed out.
Documentation: clarify how to disable elements in core.whitespace (Junio C Hamano)
Makefile: fix shell quoting (Junio C Hamano)
tests: propagate $(TAR) down from the toplevel Makefile (Junio C Hamano)
index-pack.c: correctly initialize appended objects (Björn Steinbrink)
send-email: find body-encoding correctly (Peter Valdemar Mørch)
document that git-tag can tag more than heads (Jonathan Nieder)
perl/Makefile: update NO_PERL_MAKEMAKER section (Brandon Casey)
bash: offer only paths after '--' for 'git checkout' (SZEDER Gábor)
checkout: mention '--' in the docs (SZEDER Gábor)
git-checkout: improve error messages, detect ambiguities. (Pierre Habouzit)
update test case to protect am --skip behaviour (Olivier Marin)
Teach fsck and prune about the new location of temporary objects (Brandon Casey)
git-checkout: fix command line parsing. (Pierre Habouzit)
At this point immediately before -rc1, I am giving much higher precedence
to real fixes than clean-ups, "use parse-opt", or new features. Please do
not get alarmed if your non-fix patches are left unresponded for a while.
BTW, has anybody taken a look at this one?
Subject: BUG: fetch incorrect interpretation of globing patterns in refspecs
Date: Thu, 24 Jul 2008 09:07:21 +0200
Message-ID: <71295b5a0807240007k246973abj1897895d0d67bb6c@mail.gmail.com>
If not, I think I probably need to take a look at this, reproducing and
possibly fixing, before applying non-fix patches.
next prev parent reply other threads:[~2008-07-25 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 23:13 [PATCH] bash completion: Add completion for 'git help' Lee Marlow
2008-07-24 0:07 ` Lee Marlow
2008-07-25 20:40 ` Shawn O. Pearce
2008-07-25 21:02 ` Junio C Hamano [this message]
2008-07-26 8:24 ` fetch refspec foo/* matches foo* Jeff King
2008-07-26 8:33 ` Jeff King
2008-07-26 13:13 ` [PATCH] init: handle empty "template" parameter, was " Johannes Schindelin
2008-07-28 6:02 ` Jeff King
2008-07-28 6:13 ` Junio C Hamano
2008-07-28 6:16 ` Jeff King
2008-07-27 0:18 ` Junio C Hamano
2008-07-27 6:15 ` [PATCH] make sure parsed wildcard refspec ends with slash Junio C Hamano
2008-07-27 17:20 ` Daniel Barkalow
2008-07-28 5:41 ` Jeff King
2008-07-24 0:08 ` [PATCH] bash completion: Add completion for 'git help' Lee Marlow
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v1w1hsmnc.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lee.marlow@gmail.com \
--cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).