zsh-workers
 help / color / mirror / code / Atom feed
From: Nikolai Weibull <now@bitwi.se>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: nits with new _git
Date: Tue, 17 May 2011 15:02:13 +0200	[thread overview]
Message-ID: <BANLkTim3=-aBJeW7DqSCo=QVSyEE4Sua0A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTim1YO+R1uz7gfribU1G-UrfS8NwiQ@mail.gmail.com>

On Sat, May 14, 2011 at 03:46, Mikael Magnusson <mikachu@gmail.com> wrote:
> Also noticed now, some options that take numbers just show '-M' as the
> description instead of the actual string. For example git tag -n <tab>
> and git fast-export --progress=<tab>, while git config
> gui.blamehistoryctx <tab> properly shows 'number of days'.

This is a problem with __git_guard_* not checking for compadd options.
 I’ll fix it tonight.

Is there any way that I could get commit access to

Completion/Unix/Command/_git

so that I can fix smaller issues like this one without first posting a
[PATCH] to zsh-workers?  I’m worried that the flood of smaller patches
drown out important ones and also may result in some going missed.

If so, my user name on SourceForge is pcppopper.

Thanks!


  parent reply	other threads:[~2011-05-17 13:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-14  1:28 Mikael Magnusson
2011-05-14  1:46 ` Mikael Magnusson
2011-05-14  8:38   ` Nikolai Weibull
2011-05-17 13:02   ` Nikolai Weibull [this message]
2011-05-14  3:13 ` build problem with patch level 1.5301 S. Cowles
2011-05-14  4:00   ` Bart Schaefer
2011-05-14 16:22     ` Peter Stephenson
2011-05-17 12:56 ` nits with new _git Nikolai Weibull
2011-05-29 15:11   ` Nikolai Weibull
2011-06-03 21:39   ` Mikael Magnusson
2011-07-20 11:28     ` Nikolai Weibull
2011-07-21  9:06       ` Nikolai Weibull
2011-07-21  9:57         ` Mikael Magnusson

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='BANLkTim3=-aBJeW7DqSCo=QVSyEE4Sua0A@mail.gmail.com' \
    --to=now@bitwi.se \
    --cc=mikachu@gmail.com \
    --cc=zsh-workers@zsh.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://git.vuxu.org/mirror/zsh/

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).