public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Lancelot SIX <lsix@lancelotsix.com>
To: Tom Tromey <tom@tromey.com>
Cc: Mark Wielaard <mark@klomp.org>,
	Luis Machado <luis.machado@arm.com>,
	Simon Marchi <simark@simark.ca>,
	"gdb@sourceware.org" <gdb@sourceware.org>,
	John Baldwin <jhb@FreeBSD.org>
Subject: Re: Any concrete plans after the GDB BoF?
Date: Fri, 27 Jan 2023 15:50:16 +0000	[thread overview]
Message-ID: <20230127155016.zchm4tsawlkdfyne@ubuntu.lan> (raw)
In-Reply-To: <87bkmtx83b.fsf@tromey.com>

On Fri, Jan 20, 2023 at 01:30:00PM -0700, Tom Tromey wrote:
> Mark> I use git-pw for that:
> Mark> https://patchwork.readthedocs.io/projects/git-pw/
> 
> Tom> Just to be clear -- I think if people want to use git-pw, they should,
> Tom> and shouldn't wait for some official blessing.
> 
> I gave it a look today.  There were 8 pages of patches, but nearly all
> of them have been checked in.  I went through and cleaned out a few
> pages, but TBH this is pretty boring, not to mention error-prone.
> 
> Tom

Hi,

I usually try to run a script doing this automatically.  However, it can
only detect when a checked-in patch exactly matches what have been sent
to the ML.  So the situations where we have "OK to merge with this
detail fixed" will not be caught by the script.

Also, I wish patchwork could automatically close a patches/series when a new
revision is sent to the ML. This is another class of patches which
remain on patchwork when they should probably not.  I did try to close
those manually in the past, but got overwhelmed, so I do not do that
anymore.

That being said, I still use git-pw to fetch and apply patch and series.
This is really convenient when I am not working on the host where I have
my mail client.

Lancelot.

  reply	other threads:[~2023-01-27 15:51 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 10:47 Luis Machado
2022-10-28 16:16 ` Simon Marchi
2022-10-28 16:51   ` John Baldwin
2022-10-28 16:54     ` Simon Marchi
2022-10-31  9:28   ` Luis Machado
2022-10-31 13:17     ` Simon Marchi
2022-10-31 13:37       ` Joel Brobecker
2022-10-31 14:15         ` Simon Marchi
2022-10-31 17:31           ` Joel Brobecker
2023-02-11 17:13           ` Andrew Burgess
2023-02-12 12:43             ` Mark Wielaard
2023-02-13 11:54               ` Andrew Burgess
2023-02-13 12:52                 ` Luis Machado
2023-02-13 14:24                   ` Tom Tromey
2023-02-13 14:42                     ` Luis Machado
2023-02-13 15:13                   ` Andrew Burgess
2023-02-13 15:23                     ` Luis Machado
2023-02-14  5:48                       ` Joel Brobecker
2023-02-15 14:47                         ` Andrew Burgess
2023-02-16  4:14                           ` Joel Brobecker
2023-02-16  9:51                           ` Mark Wielaard
2023-02-16 10:16                             ` Joel Brobecker
2023-02-16 11:58                               ` Eli Zaretskii
2023-02-16 13:31                                 ` Joel Brobecker
2023-02-16 15:23                                   ` Eli Zaretskii
2023-02-14 13:07                   ` Mark Wielaard
2023-02-14 14:23                   ` Pedro Alves
2023-02-14 13:00                 ` Mark Wielaard
2023-02-15 14:36                   ` Andrew Burgess
2023-02-13 14:05             ` Tom Tromey
2022-12-15 10:17     ` Luis Machado
2023-01-01 22:02     ` Mark Wielaard
2023-01-20 17:30       ` Tom Tromey
2023-01-20 20:30         ` Tom Tromey
2023-01-27 15:50           ` Lancelot SIX [this message]
2023-01-27 23:50             ` Tom Tromey
2023-01-30 17:43               ` Lancelot SIX
2023-01-30 18:46                 ` Mark Wielaard
2023-01-30 21:08                   ` Tom Tromey
2023-02-04 11:36                     ` Mark Wielaard
2023-01-31 10:00                   ` Lancelot SIX
2022-12-13  2:48 ` Frank Ch. Eigler
2023-02-16  8:53 anix

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=20230127155016.zchm4tsawlkdfyne@ubuntu.lan \
    --to=lsix@lancelotsix.com \
    --cc=gdb@sourceware.org \
    --cc=jhb@FreeBSD.org \
    --cc=luis.machado@arm.com \
    --cc=mark@klomp.org \
    --cc=simark@simark.ca \
    --cc=tom@tromey.com \
    /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).