git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2013, #03; Thu, 6)
Date: Sun, 9 Jun 2013 23:48:33 +0200	[thread overview]
Message-ID: <20130609214833.GE2091@goldbirke> (raw)
In-Reply-To: <7v1u8bouam.fsf@alter.siamese.dyndns.org>

Hi,


On Sun, Jun 09, 2013 at 02:20:33PM -0700, Junio C Hamano wrote:
> Regarding that rr/complete-difftool topic, let's revert the tip 2
> commits (the "ls-tree, archive and show" one, and the follow-up
> resurrection of __git_complete_file) with this:
> 
>     Revert 77c1305 and 3c3b46b
>     
>     As explained by SZEDER Gábor in $gmane/226272, git_complete_file
>     helper is about completing <tree-ish>, taking <commit> at the tips
>     of refs and also understanding <tree-ish>:<path> notation, and
>     changing "archive" and "ls-tree" to use git_complete_revlist_file
>     that in addition is meant to expand A..B range notation was a
>     mistake.
>     
>     Signed-off-by: Junio C Hamano <gitster@pobox.com>
> 
> and then queue this on top of d8517cc6670d (completion: difftool
> takes both revs and files, 2013-06-02), so that the attached and
> d8517cc6670d will be the only two commits that graduate to 'master'
> from this topic.

That's fine with me, except ...

> -- >8 --
> From: Ramkumar Ramachandra <artagnon@gmail.com>
> Date: Sun, 2 Jun 2013 19:33:42 +0530
> Subject: [PATCH] completion: show can take both revlist and paths
> 
> The 'git show' completion uses __git_complete_file (aliased to
> __git_complete_revlist_file), because accepts <tree-ish>:<path> as
> well as <commit-ish>.  But the command also accepts range of commits
> in A..B notation, so using __git_complete_revlist_file is more
> appropriate.
> 
> There still remain two users of __git_complete_file, completions for
> "archive" and "ls-tree".  As these commands do not take range
> notation, and "git show" no longer uses __git_complete_file, the
> implementation of can be updated not to complete ranges, but that is

"the implementation of" what?  A word missing perhaps?  Or "the
implementation can be updated"?


Best,
Gábor

> a separate topic.
> 
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>  contrib/completion/git-completion.bash | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index 1b4b0f9..b9dfc3b 100644
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -2360,7 +2360,7 @@ _git_show ()
>  		return
>  		;;
>  	esac
> -	__git_complete_file
> +	__git_complete_revlist_file
>  }
>  
>  _git_show_branch ()
> -- 
> 1.8.3-477-gc2fede3

  reply	other threads:[~2013-06-09 21:48 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
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 [this message]
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=20130609214833.GE2091@goldbirke \
    --to=szeder@ira.uka.de \
    --cc=artagnon@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).