threads / patch / 44613

patchCompletion: Add support for --submodule=diff

Subject: [PATCH] Completion: Add support for --submodule=diff

## tl;dr

6 messages between Dec 4, 2016 and Feb 6, 2017. Diffs are folded; open one to read it.

replies: 5people: 4as markdown or json

peterjclaw@gmail.com· Dec 4, 2016, 14:41 UTC · lore
From: Peter Law <PeterJCLaw@gmail.com>

Teach git-completion.bash about the 'diff' option to 'git diff --submodule=', which was added in Git 2.11.

Signed-off-by: Peter Law <PeterJCLaw@gmail.com>
---
 contrib/completion/git-completion.bash | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Show changes to contrib/completion/git-completion.bash +1 −1
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index 21016bf8d..ab11e7371 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -1206,7 +1206,7 @@ _git_describe ()
 
 __git_diff_algorithms="myers minimal patience histogram"
 
-__git_diff_submodule_formats="log short"
+__git_diff_submodule_formats="diff log short"
 
 __git_diff_common_options="--stat --numstat --shortstat --summary
 			--patch-with-stat --name-only --name-status --color
-- 
2.11.0
Peter Law· Jan 30, 2017, 21:13 UTC · re: peterjclaw@gmail.com · lore

Re: [PATCH] Completion: Add support for --submodule=diff

Hi,
> Teach git-completion.bash about the 'diff' option to 'git diff
> --submodule=', which was added in Git 2.11.

I posted this patch back in December, but I've not heard anything. I'm sure as maintainers you're all quite busy, but I was wondering how long it usually takes to get a response to patches? (also whether I'd gotten some part of the submission process wrong?)

Thanks, Peter

Brandon Williams· Jan 30, 2017, 21:43 UTC · re: Peter Law · lore

Re: [PATCH] Completion: Add support for --submodule=diff

On 01/30, Peter Law wrote:
Show 12 quoted lines
> Hi,
> 
> > Teach git-completion.bash about the 'diff' option to 'git diff
> > --submodule=', which was added in Git 2.11.
> 
> I posted this patch back in December, but I've not heard anything. I'm
> sure as maintainers you're all quite busy, but I was wondering how
> long it usually takes to get a response to patches? (also whether I'd
> gotten some part of the submission process wrong?)
> 
> Thanks,
> Peter

It looks like this must have just fallen through the cracks. Your patch looks good to me and works when I test it locally.

-- 
Brandon Williams
Junio C Hamano· Jan 30, 2017, 23:03 UTC · re: Peter Law · lore

Re: [PATCH] Completion: Add support for --submodule=diff

Peter Law <peterjclaw@gmail.com> writes:
Show 7 quoted lines
>> Teach git-completion.bash about the 'diff' option to 'git diff
>> --submodule=', which was added in Git 2.11.
>
> I posted this patch back in December, but I've not heard anything. I'm
> sure as maintainers you're all quite busy, but I was wondering how
> long it usually takes to get a response to patches? (also whether I'd
> gotten some part of the submission process wrong?)

When there is clear "subsystem maintainer(s)" in the area, I try to refrain from commenting until they speak up, and completion scripts are one of these areas. I usually ping them after a few days but in December with holidays and things people are usually slow, and so was I X-<.

Will pick it up. Thanks for a reminder; you absolutely did the right thing (i.e. sending it out with people who are likely to know about the area CC'ed, waiting for a while and then sending a reminder).

Peter Law· Feb 6, 2017, 22:56 UTC · re: Junio C Hamano · lore

Re: [PATCH] Completion: Add support for --submodule=diff

Hi,
Junio C Hamano <gitster@pobox.com> wrote:
Show 20 quoted lines
> Peter Law <peterjclaw@gmail.com> writes:
>
>>> Teach git-completion.bash about the 'diff' option to 'git diff
>>> --submodule=', which was added in Git 2.11.
>>
>> I posted this patch back in December, but I've not heard anything. I'm
>> sure as maintainers you're all quite busy, but I was wondering how
>> long it usually takes to get a response to patches? (also whether I'd
>> gotten some part of the submission process wrong?)
>
> When there is clear "subsystem maintainer(s)" in the area, I try to
> refrain from commenting until they speak up, and completion scripts
> are one of these areas.  I usually ping them after a few days but in
> December with holidays and things people are usually slow, and so
> was I X-<.
>
> Will pick it up.  Thanks for a reminder; you absolutely did the
> right thing (i.e. sending it out with people who are likely to know
> about the area CC'ed, waiting for a while and then sending a
> reminder).
Awesome, many thanks!
Peter
Jacob Keller· Jan 31, 2017, 00:10 UTC · re: peterjclaw@gmail.com · lore

Re: [PATCH] Completion: Add support for --submodule=diff

On Sun, Dec 4, 2016 at 6:41 AM,  <peterjclaw@gmail.com> wrote:
Show 26 quoted lines
> From: Peter Law <PeterJCLaw@gmail.com>
>
> Teach git-completion.bash about the 'diff' option to 'git diff
> --submodule=', which was added in Git 2.11.
>
> Signed-off-by: Peter Law <PeterJCLaw@gmail.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 21016bf8d..ab11e7371 100644
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -1206,7 +1206,7 @@ _git_describe ()
>
>  __git_diff_algorithms="myers minimal patience histogram"
>
> -__git_diff_submodule_formats="log short"
> +__git_diff_submodule_formats="diff log short"
>
>  __git_diff_common_options="--stat --numstat --shortstat --summary
>                         --patch-with-stat --name-only --name-status --color
> --
> 2.11.0
>
Yep, this looks good to me.

Thanks, Jake

← back to recent threads