From: "Raghav Gururajan" <raghavgururajan@disroot.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 38954@debbugs.gnu.org
Subject: [bug#38954] gnu: gnome: Add missing inputs.
Date: Wed, 08 Jan 2020 09:32:38 +0000 [thread overview]
Message-ID: <8ad95c122bd6608e8d19ed0e58236d80@disroot.org> (raw)
In-Reply-To: <20200108004128.46d93ac0@tachikoma.lepiller.eu>
Hello Jan!
> you've built a maze of patches which makes it difficult for us (at
> least for me) to review. I'd like to encourage you to report all of
> these patches under only one bug. You can use apply all your patches
> locally on a single branch, and use git send-email (from git:send-email
> package) to send and format the messages properly. Please add them in
> an order that makes sense (dependencies first) so that at every commit,
> everything builds fine.
>
> Thanks in advance!
Sorry that I created confusion. I will do it better with future patches.
For these, let me put a flow chart for the order in which the patches are to be pushed.
[1] 38904
[2] 38905
[3] 38906
[4] 38914 (38894 --> 38896 --> 38898 --> 38901 --> 38914)
[5] 38911 (38909 --> 38911)
[6] 38931 (38930 --> 38931)
[7] 38953
[8] 38935
[9] 38954
Please let me know if you have any questions.
Thank you!
Regards,
RG.
next prev parent reply other threads:[~2020-01-08 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 19:37 [bug#38954] gnu: gnome: Add missing inputs Raghav Gururajan
2020-01-07 23:41 ` Julien Lepiller
2020-01-08 9:32 ` Raghav Gururajan [this message]
2020-01-12 21:04 ` [bug#38954] v3 Raghav Gururajan
2020-01-23 1:54 ` Danny Milosavljevic
2022-01-07 4:47 ` [bug#38954] gnu: gnome: Add missing inputs Maxim Cournoyer
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=8ad95c122bd6608e8d19ed0e58236d80@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=38954@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.