Hi,
09/03/2020 15:04, Daniel Shahaf :
> Thanks, v2 looks good. Would you please post it to zsh-work...@zsh.org?
> I could just commit it upstream, but I'd like to have a second pair of eyes
> over it.
I will send the patch now and put you in CC for handling the final
details before merge.
>> +
Control: forwarded -1 workers/45524
Romain Porte wrote on Mon, 09 Mar 2020 14:45 +00:00:
> 09/03/2020 15:04, Daniel Shahaf :
> >> +'*:dsc file:_files -g "*.{changes,dsc}(-.)"'
> > In this line —
> >
> > 1. You may need to change «{foo,bar}» to «(foo|bar)» to avoid NO_MATCH
> > errors
> > when
Romain Porte wrote on Mon, Mar 09, 2020 at 10:33:29 +0100:
> Hello,
>
> 09/03/2020 02:51, Daniel Shahaf :
> > Thanks. Upstreaming would consist of emailing the patch to
> > zsh-work...@zsh.org and updating the metadata on this bug. However,
> > have you considered proposing the completion for in
Hello,
09/03/2020 02:51, Daniel Shahaf :
> Thanks. Upstreaming would consist of emailing the patch to
> zsh-work...@zsh.org and updating the metadata on this bug. However,
> have you considered proposing the completion for inclusion in
> devscripts, alongside dscverify(1) and its bash completion
Control: tags -1 confirmed
Control: affects -1 devscripts
Romain Porte wrote on Sun, 08 Mar 2020 21:50 +0100:
> I would be happy to help in the upstreaming process if you find it
> welcome. I prefer to create this bug first to avoid duplicate work
> and because this completion is Debian-specific,
Package: zsh-common
Version: 5.8-3
Severity: normal
Tags: patch upstream
Dear Maintainer,
As I was playing with some of the devtools, I found that the `dscverify`
program did not have any completion. The devtools package provides a
bash completion, but not a zsh one, unfortunately.
Hence I took
6 matches
Mail list logo
