all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	GLIBC Devel <libc-alpha@sourceware.org>,
	gdb-patches@sourceware.org, help-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Tue, 03 Dec 2019 12:07:00 -0700	[thread overview]
Message-ID: <87fti1cjor.fsf@tromey.com> (raw)
In-Reply-To: <1277b1bb-c3c4-6fc8-a700-c7207efd31cf@gotplt.org> (Siddhesh Poyarekar's message of "Thu, 28 Nov 2019 11:17:16 +0530")

>>>>> "Siddhesh" == Siddhesh Poyarekar <siddhesh@gotplt.org> writes:

>> Or do you have something else, i.e. not just an upgrade, in mind?

Siddhesh> To begin with, I intend to add hooks to close patchwork patches on merge
Siddhesh> so that that aspect is automated.  It was the one problem we had with
Siddhesh> patchwork and with ChangeLogs gone in glibc, we're definitely a lot more
Siddhesh> likely to get close to that goal.

For gdb, I'd like this to be much more reliable than it is today.  We
were thinking we'd simply add a kind of patch-id to the commit message
-- the way we're currently doing with gerrit -- and then have patchworks
recognize this ID and use it as its internal key.

I think this is not a very large amount of work in patchworks.

Tom

  parent reply	other threads:[~2019-12-03 19:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org>
2019-11-28  5:04 ` Fwd: [X-POST] patchwork.sourceware.org refresh Siddhesh Poyarekar
     [not found] ` <alpine.LFD.2.21.1911280509420.3472978@eddie.linux-mips.org>
2019-11-28  5:47   ` Siddhesh Poyarekar
2019-11-28 15:47     ` Carlos O'Donell
2019-11-30 11:35     ` Maciej W. Rozycki
2019-12-01  4:35       ` Siddhesh Poyarekar
2019-12-01 16:26       ` Siddhesh Poyarekar
2019-12-03 19:07     ` Tom Tromey [this message]
2019-12-04  1:05       ` Carlos O'Donell
2019-12-08 12:06 ` Siddhesh Poyarekar
2019-12-08 12:10   ` Florian Weimer
2019-12-08 12:21     ` Christian Brauner
2019-12-09  7:56       ` Siddhesh Poyarekar
2019-12-09 16:52         ` Konstantin Ryabitsev
2019-12-09 16:59           ` Siddhesh Poyarekar
2019-12-09 15:44   ` Sergio Durigan Junior
2019-12-09 16:56     ` Siddhesh Poyarekar
2019-12-09 17:15       ` Sergio Durigan Junior
2020-01-14 19:05         ` Christian Biesinger
2020-01-15  2:33           ` 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=87fti1cjor.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=help-guix@gnu.org \
    --cc=libc-alpha@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=siddhesh@gotplt.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.