From: Bert Wesarg <bert.wesarg@googlemail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Todd Zullinger <tmz@pobox.com>, Jeff King <peff@peff.net>,
james bardin <jbardin@bu.edu>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] completion: Replace config --list with --get-regexp
Date: Sun, 13 Sep 2009 12:51:05 +0200 [thread overview]
Message-ID: <36ca99e90909130351m7ad5a641t8adb3ade3d2ec5ca@mail.gmail.com> (raw)
In-Reply-To: <20090912183139.GO1033@spearce.org>
On Sat, Sep 12, 2009 at 20:31, Shawn O. Pearce <spearce@spearce.org> wrote:
> Todd Zullinger <tmz@pobox.com> wrote:
>> James Bardin noted that the completion spewed warnings when no git
>> config file is present. This is likely a bug to be fixed in git config,
>> but it's also a good excuse to simplify the completion code by using the
>> --get-regexp option as Jeff King pointed out.
>>
>> Signed-off-by: Todd Zullinger <tmz@pobox.com>
>
> Thanks, looks good.
I have not looked into this, but what about pushurl?
Bert
next prev parent reply other threads:[~2009-09-13 10:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 15:13 bash_completion outside repo james bardin
2009-09-11 13:11 ` Michael J Gruber
2009-09-11 13:33 ` Todd Zullinger
2009-09-11 14:00 ` james bardin
2009-09-11 14:17 ` Jeff King
2009-09-11 14:36 ` Shawn O. Pearce
2009-09-11 15:09 ` Jeff King
2009-09-11 16:47 ` Jeff King
2009-09-11 20:43 ` Junio C Hamano
2009-09-11 21:12 ` Jeff King
2009-09-11 21:22 ` Junio C Hamano
2009-09-11 21:29 ` Jeff King
2009-09-11 21:57 ` Junio C Hamano
2009-09-11 22:04 ` Junio C Hamano
2009-09-11 22:05 ` Jeff King
2009-09-11 23:23 ` [PATCH] completion: Replace config --list with --get-regexp Todd Zullinger
2009-09-12 18:31 ` Shawn O. Pearce
2009-09-13 10:51 ` Bert Wesarg [this message]
2009-09-13 18:29 ` Todd Zullinger
2009-09-13 20:40 ` Junio C Hamano
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=36ca99e90909130351m7ad5a641t8adb3ade3d2ec5ca@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jbardin@bu.edu \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=tmz@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).