public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: DJ Delorie <dj@redhat.com>, Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Run TryBot-apply_patch on the full queue?
Date: Tue, 20 Sep 2022 10:39:08 -0400	[thread overview]
Message-ID: <13b6494d-7786-bc72-ceac-b0907017c6a9@gotplt.org> (raw)
In-Reply-To: <xnwn9yyvdp.fsf@greed.delorie.com>

On 2022-09-20 10:26, DJ Delorie wrote:
> But signed emails won't solve Siddhesh's request of retrying every
> pending patch every day, because they won't be signed.

I can very simply do this from the automation I implemented to update 
committed patch states, I don't think signed emails are needed for that.

Sid

      reply	other threads:[~2022-09-20 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 13:31 Siddhesh Poyarekar
2022-09-19 13:38 ` Siddhesh Poyarekar
2022-09-19 16:49 ` DJ Delorie
2022-09-19 19:46   ` Carlos O'Donell
2022-09-19 19:55     ` DJ Delorie
2022-09-20 10:21       ` Carlos O'Donell
2022-09-20 14:26         ` DJ Delorie
2022-09-20 14:39           ` Siddhesh Poyarekar [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=13b6494d-7786-bc72-ceac-b0907017c6a9@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=carlos@redhat.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).