all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Tai <atai@atai.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
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 08:59:14 -0700	[thread overview]
Message-ID: <CAJsg1E_tZ7vVgpkBxZTBGG--Tk1xcU=0uorP4iT4+vwwAd3+vg@mail.gmail.com> (raw)
In-Reply-To: <8734yay3yb.fsf@gmail.com>

Maxim, I know about this.  Problem is Guix QA does not look at old issues

On Mon, Oct 16, 2023 at 8:36 AM Maxim Cournoyer
<maxim.cournoyer@gmail.com> wrote:
>
> 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.
>
> 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).
>


  reply	other threads:[~2023-10-16 16:01 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
2023-10-16 15:59   ` Andy Tai [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJsg1E_tZ7vVgpkBxZTBGG--Tk1xcU=0uorP4iT4+vwwAd3+vg@mail.gmail.com' \
    --to=atai@atai.org \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.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.
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.