public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: GLIBC Devel <libc-alpha@sourceware.org>
Subject: Sourceware patchwork instance is up
Date: Thu, 30 Apr 2020 08:22:59 +0530	[thread overview]
Message-ID: <fd33690f-a2a0-62b9-a225-427515629714@gotplt.org> (raw)

Hello,

The patchwork instance on sourceware is finally up again at
patchwork.sourceware.org.  It is missing most patches between 24th April
and today; I'll import those over the weekend.

Many thanks to Frank Eigler for bearing with my general incompetence
with all things system admin (or devops as the young folks call it this
days) and helping get the instance up.

Here's a quick rundown on status:

- The instance is based on the tip of the 2.2 stable branch

- The instance handles DMARC related issues well as is evident from the
patches I imported manuall

- Next step is to add git hooks and scripts to automatically manage
patch state.  I haven't been able to figure out how the Tags work;
patchwork claims to identify and act on Tags, but I don't know how it
does that.

- We need to figure out what to do with very old patches, i.e. > 2 years
old.  Maybe we should mark them as 'Not Applicable' or similar and leave
them?

Apologies that the instance took so long to bring up; I've been crunched
for time and something or the other kept coming up.  If someone has
bandwidth to help with the git hooks, I'd be more than happy to hand
that bit over to you.  If not, it'll have to wait for another free block
of time some time later.

Siddhesh

PS: Now on to the ChangeLog script bugs that people reported months ago!

             reply	other threads:[~2020-04-30  2:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  2:52 Siddhesh Poyarekar [this message]
2020-05-04 12:40 ` Florian Weimer
2020-05-04 18:59   ` Siddhesh Poyarekar

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=fd33690f-a2a0-62b9-a225-427515629714@gotplt.org \
    --to=siddhesh@gotplt.org \
    --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).