From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Tomasz Jeneralczyk <tj@schwi.pl>
Cc: 56276@debbugs.gnu.org
Subject: [bug#56276] [PATCH 1/2] gnu: gdk-pixbuf: Remove unnecessary dependency.
Date: Tue, 28 Jun 2022 15:49:25 +0200 [thread overview]
Message-ID: <3ac3419ef08742e5a1b377ff0f489ef42c73522b.camel@ist.tugraz.at> (raw)
In-Reply-To: <a3cffdc1e4b05621de14a6afd337da65@schwi.pl>
Am Dienstag, dem 28.06.2022 um 13:45 +0000 schrieb Tomasz Jeneralczyk:
> On 2022-06-28 12:38, Liliana Marie Prikler wrote:
> > This patch should go to core-updates, while 2/2 can go to master.
>
> Should I send the patched here as [PATCH v2 1/2 core-updates] and
> [PATCH v2 2/2], or split it into two new patches?
> Sorry, it's just not clear to me.
The way you propose is *probably* fine. It's rather rare that patches
"need" to be split in this manner. FWIW I'd propose swapping the
patches around, so that [1/2] can go to master and [2/2] to core-
updates.
> I also noticed I gave the 1/2 an incorrect changelog - it should be
> `propagated-inputs` instead of `native-inputs`. I'll fix that too.
Please do.
Cheers
next prev parent reply other threads:[~2022-06-28 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 13:09 [bug#56276] [PATCH 0/2] gnu: Add gdk-pixbuf-xlib Tomasz Jeneralczyk
2022-06-28 13:21 ` [bug#56276] [PATCH 1/2] gnu: gdk-pixbuf: Remove unnecessary dependency Tomasz Jeneralczyk
2022-06-28 12:38 ` Liliana Marie Prikler
2022-06-28 13:45 ` Tomasz Jeneralczyk
2022-06-28 13:49 ` Liliana Marie Prikler [this message]
2022-06-28 13:21 ` [bug#56276] [PATCH 2/2] gnu: Add gdk-pixbuf-xlib Tomasz Jeneralczyk
2022-06-28 16:15 ` [bug#56276] [PATCH v2 1/2] " Tomasz Jeneralczyk
2022-06-28 16:15 ` [bug#56276] [PATCH core-updates v2 2/2] gnu: gdk-pixbuf: Remove unnecessary dependency Tomasz Jeneralczyk
2022-07-02 11:54 ` bug#56276: [PATCH v2 1/2] gnu: Add gdk-pixbuf-xlib Liliana Marie Prikler
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=3ac3419ef08742e5a1b377ff0f489ef42c73522b.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56276@debbugs.gnu.org \
--cc=tj@schwi.pl \
/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).