From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: How to send revision patches to old issues in DEBBUGS so Guix QA can look at them?
Date: Mon, 16 Oct 2023 11:36:28 -0400 [thread overview]
Message-ID: <8734yay3yb.fsf@gmail.com> (raw)
In-Reply-To: <CAJsg1E9qUpYkyiR7pHy_CdeMQ58362=OL-dCLojL3zXG2pwosA@mail.gmail.com> (Andy Tai's message of "Sat, 14 Oct 2023 13:46:17 -0700")
Hi Andy,
Andy Tai <atai@atai.org> writes:
> Hi, per Chris's recent comments, Guix QA only looks at (a window of)
> recently created issues due to storage space limitations, which is
> understandable.
>
> However, if I have update (package definition) patches to not very
> recent issues, such as some stale issues sitting there for some time,
> Guix QA does not pick these revisions up. Then these revisions will
> not be reviewed and would not be merged.
>
> Ideally, Guix QA should look at recent patch submissions to the
> guix-patches mailing list but not sure if that is easy to implement.
>
> Then what is the best way to make recent patches to old issues covered
> by Guix QA? I tried to create new issues and then merge old issues
> into the new ones but that is probably not a good way to go or good
> thing to do.
After rebasing the old series locally, you can send it to the *same bug
ID* with a bumped version (e.g. git send-email -v2
... --to=NNNNN@debbugs.gnu.org).
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-16 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 20:46 How to send revision patches to old issues in DEBBUGS so Guix QA can look at them? Andy Tai
2023-10-16 15:36 ` Maxim Cournoyer [this message]
2023-10-16 15:59 ` Andy Tai
2023-10-16 16:26 ` Maxim Cournoyer
2023-10-17 17:39 ` Christopher Baines
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734yay3yb.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=atai@atai.org \
--cc=guix-devel@gnu.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.savannah.gnu.org/cgit/guix.git
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).