From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: Danny Milosavljevic <dannym@scratchpost.org>, 41111@debbugs.gnu.org
Subject: [bug#41111] Claws-Mail
Date: Wed, 30 Sep 2020 12:52:04 +0200 [thread overview]
Message-ID: <87v9fvzgdn.fsf@nckx> (raw)
In-Reply-To: <d95e34dc-cc97-1033-de64-b31b9071115e@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Raghav,
Raghav Gururajan 写道：
> Based on your feedback, I have split the changes. Please find
> the
> attached patches.
I haven't been following this thread, but have updated claws-mail
to .7 on master in the meantime.
Your 0003-gnu-claws-mail-Update-to-3.17.7.patch does unrelated
things and deserves a different commit message.
> [source]<origin>[sha256]: Modify base32.
This isn't needed; <version> and <origin> changes are implicitly
covered by ‘Update to x.y’ to reduce noise in the common case.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-09-30 10:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 13:06 [bug#41111] gnu: claws-mail: Fix fhs directories Raghav Gururajan
2020-05-08 17:29 ` [bug#41111] claws-mail Danny Milosavljevic
2020-09-02 14:50 ` Ludovic Courtès
2020-09-30 10:17 ` [bug#41111] Claws-Mail Raghav Gururajan
2020-09-30 10:52 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-10-15 3:05 ` Raghav Gururajan
2020-10-15 9:14 ` bug#41111: Claws-Mail Danny Milosavljevic
2020-10-15 16:40 ` [bug#41111] Claws-Mail Raghav Gururajan
2020-10-15 20:07 ` Danny Milosavljevic
2020-10-15 20:08 ` Raghav Gururajan
2020-10-15 22:42 ` Danny Milosavljevic
2020-10-15 22:48 ` Raghav Gururajan
2020-10-15 22:52 ` Raghav Gururajan
2020-10-16 9:48 ` Danny Milosavljevic
2020-10-16 19:54 ` Raghav Gururajan
2020-10-17 10:08 ` Danny Milosavljevic
2020-10-17 11:26 ` Raghav Gururajan
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=87v9fvzgdn.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=41111@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=me@tobias.gr \
--cc=raghavgururajan@disroot.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 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.