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 (Jun 2013, #03; Thu, 6)
Date: Fri, 7 Jun 2013 21:34:44 +0200 [thread overview]
Message-ID: <20130607193444.GB31625@goldbirke> (raw)
In-Reply-To: <7vli6mwx07.fsf@alter.siamese.dyndns.org>
On Thu, Jun 06, 2013 at 06:05:44PM -0700, Junio C Hamano wrote:
> SZEDER Gábor <szeder@ira.uka.de> writes:
>
> > On Thu, Jun 06, 2013 at 03:41:08PM -0700, Junio C Hamano wrote:
> >> * rr/complete-difftool (2013-06-03) 2 commits
> >> (merged to 'next' on 2013-06-04 at 01c7611)
> >> + completion: clarify ls-tree, archive, show completion
> >> + completion: difftool takes both revs and files
> >>
> >> Update command line completion (in contrib/) to use a better named
> >> completion helper function for commands that take revisions and
> >> paths.
> >>
> >> Will merge to 'master'.
> >
> > This should not be merged to master as is; the one at the top because
> > of the reasons given in $gmane/226272, the one at the bottom because
> > of the misleading commit message (__git_complete_file() always
> > completed refs first as part of the ref:file notation, so it worked
> > just fine except for the ref1...ref2 notation; the real reason for
> > calling __git_complete_revlist_file() for difftool is to make clear
> > that difftool takes ref1...ref2:file, too).
>
> Oops.
>
> It is too late to amend the log messages now, but at least a follow-up
> patch can fix the breakage by adding __git_complete_file() back. Would
> you mind doing that?
Is it in master already? Am I missing something?
Wouldn't it be cleaner to revert those two patches from next and apply
this instead?
-- >8 --
From: SZEDER Gábor <szeder@ira.uka.de>
Subject: [PATCH] completion: be explicit about revlist completion for difftool
and show
The completion functions for 'git difftool' and 'git show' call
__git_complete_file() to support completion of the 'ref:path' notation.
However, these two commands also understand the 'ref1..ref2:path'
notation, the completion of which we happen to support accidentaly,
because nowadays __git_complete_file() is a wrapper around
__git_complete_revlist_file().
Let's be explicit about it and call __git_complete_revlist_file()
directly.
Signed-off-by: SZEDER Gábor <szeder@ira.uka.de>
---
contrib/completion/git-completion.bash | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index 56c52c66..fd9a1d5f 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -1211,7 +1211,7 @@ _git_difftool ()
return
;;
esac
- __git_complete_file
+ __git_complete_revlist_file
}
__git_fetch_options="
@@ -2277,7 +2277,7 @@ _git_show ()
return
;;
esac
- __git_complete_file
+ __git_complete_revlist_file
}
_git_show_branch ()
--
1.8.0.220.g4d14ece
next prev parent reply other threads:[~2013-06-07 19:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 22:41 What's cooking in git.git (Jun 2013, #03; Thu, 6) Junio C Hamano
2013-06-07 0:00 ` SZEDER Gábor
2013-06-07 1:05 ` Junio C Hamano
2013-06-07 15:57 ` Junio C Hamano
2013-06-07 19:34 ` SZEDER Gábor [this message]
2013-06-07 19:47 ` Ramkumar Ramachandra
2013-06-07 20:06 ` SZEDER Gábor
2013-06-07 17:30 ` Ramkumar Ramachandra
2013-06-07 18:41 ` Junio C Hamano
2013-06-07 19:01 ` Ramkumar Ramachandra
2013-06-07 19:16 ` SZEDER Gábor
2013-06-07 19:46 ` Junio C Hamano
2013-06-07 20:44 ` SZEDER Gábor
2013-06-07 21:53 ` Junio C Hamano
2013-06-08 0:11 ` SZEDER Gábor
2013-06-09 21:20 ` Junio C Hamano
2013-06-09 21:48 ` SZEDER Gábor
2013-06-09 22:56 ` Junio C Hamano
2013-06-10 6:25 ` Ramkumar Ramachandra
2013-06-10 7:00 ` Junio C Hamano
2013-06-10 7:41 ` Ramkumar Ramachandra
2013-06-07 18:55 ` SZEDER Gábor
2013-06-08 15:30 ` Ramkumar Ramachandra
2013-06-08 18:39 ` Matthieu Moy
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=20130607193444.GB31625@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