zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Oliver Kiddle <opk@zsh.org>
Cc: zsh-workers@zsh.org
Subject: Duplicated X-Seq?  (was: Re: Re: [PATCH v2 1/3] Introduce new completion for Linux task capabilities)
Date: Mon, 29 Mar 2021 06:38:43 +0000	[thread overview]
Message-ID: <20210329063843.GL18178@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <64380-1616929063.107376@GUiZ.fSqT.1QYU>

[Arseny to BCC]

Oliver Kiddle wrote on Sun, Mar 28, 2021 at 12:57:43 +0200:
> Lawrence Velázquez wrote:
> > On Sun, Mar 21, 2021, at 9:01 AM, Arseny Maslennikov wrote:
> > > This is intended for use on Linux-based systems only.
> > > 
> > > The next patch introduces a completion for setpriv(1), which actively
> > ping for review
> 
> I've committed the updated versions of these patches. Thanks Arseny for
> contributing the functions and for dealing with our comments. If anyone
> has further comments, they can be handled with additional patches on
> top. I tweaked _setpriv in accordance with the point Mikael made about
> brace expansion being pointless for {+,-}. That's in workers/48221 but
> worryingly, that sequence number got somehow duplicated.

How so?  «< /var/mail/archives grep \^X-Seq | grep -v ': 2' | grep -15 48221»
on the server shows no anomalies.

Cheers,

Daniel


      reply	other threads:[~2021-03-29  6:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-21 13:01 [PATCH v2 1/3] Introduce new completion for Linux task capabilities Arseny Maslennikov
2021-03-21 13:01 ` [PATCH v2 2/3] Introduce new completion for setpriv(1) on Linux Arseny Maslennikov
2021-03-22 10:18   ` Mikael Magnusson
2021-03-21 13:01 ` [RFC PATCH v2 3/3] _setpriv: complete multiple --dump with argument states Arseny Maslennikov
2021-03-27 16:28   ` Lawrence Velázquez
2021-03-27 16:28 ` [PATCH v2 1/3] Introduce new completion for Linux task capabilities Lawrence Velázquez
2021-03-28 10:57   ` Oliver Kiddle
2021-03-29  6:38     ` Daniel Shahaf [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210329063843.GL18178@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=opk@zsh.org \
    --cc=zsh-workers@zsh.org \
    /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://git.vuxu.org/mirror/zsh/

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).