From: Junio C Hamano <gitster@pobox.com>
To: Marc Khouzam <marc.khouzam@gmail.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder@ira.uka.de>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Subject: Re: [PATCH v3] Completion must sort before using uniq
Date: Sat, 24 Nov 2012 22:32:52 -0800 [thread overview]
Message-ID: <7vtxsexkdn.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAFj1UpH8h6c7xHuRG6F+pLy5YMvsJ0QdXsotCpLKnht0PsdiNw@mail.gmail.com> (Marc Khouzam's message of "Fri, 23 Nov 2012 09:02:22 -0500")
Marc Khouzam <marc.khouzam@gmail.com> writes:
> The user can be presented with invalid completion results
> when trying to complete a 'git checkout' command. This can happen
> when using a branch name prefix that matches multiple remote branches.
>
> For example, if available branches are:
> master
> remotes/GitHub/maint
> remotes/GitHub/master
> remotes/origin/maint
> remotes/origin/master
>
> When performing completion on 'git checkout ma' the user will be
> given the choices:
> maint
> master
> ...
> When dealing with 'git checkout mai', the list will be:
> maint
> maint
Wow, the description feels a tad repetitive for a one liner (it
describes "uniq -u" without pre-sort is wrong at least three times),
it would be better than no log message ;-)
I originally thought "uniq -u" was a misspelled "sort -u" when I
first saw your shorter version, but reading the code to see what is
fed to the command made it immediately obvious "sort | uniq -u" is
the right fix. With the above explanation, you do not even need to
read the code to see what is fed to the command (it is explained ;-).
So, thanks for the fix.
prev parent reply other threads:[~2012-11-25 6:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353557598-4820-1-git-send-email-marc.khouzam@gmail.com>
2012-11-22 4:16 ` [PATCH] Completion must sort before using uniq Marc Khouzam
2012-11-23 8:09 ` Joachim Schmitz
2012-11-23 8:21 ` Felipe Contreras
2012-11-23 11:17 ` [PATCH v2] " Marc Khouzam
2012-11-23 11:34 ` Felipe Contreras
2012-11-23 14:02 ` [PATCH v3] " Marc Khouzam
2012-11-23 19:21 ` Felipe Contreras
2012-11-25 6:32 ` Junio C Hamano [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
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=7vtxsexkdn.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=marc.khouzam@gmail.com \
--cc=szeder@ira.uka.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.
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).