all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>,
	Raghav Gururajan <raghavgururajan@disroot.org>
Cc: 41111@debbugs.gnu.org
Subject: [bug#41111] claws-mail
Date: Wed, 02 Sep 2020 16:50:40 +0200	[thread overview]
Message-ID: <87ft805j27.fsf@gnu.org> (raw)
In-Reply-To: <20200508192929.07cad57b@scratchpost.org> (Danny Milosavljevic's message of "Fri, 8 May 2020 19:29:29 +0200")

Hi!

Raghav, could you take a look at Danny’s suggestions below?

  https://issues.guix.gnu.org/41111

Ludo’.

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> Hi,
>
> I think that this patch does a lot more than "Fix fhs directories".
>
> Could you split it into multiple patches, each with a high-level subject that
> allows the reviewer to find out the reason for it?




  reply	other threads:[~2020-09-02 14:51 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 [this message]
2020-09-30 10:17 ` [bug#41111] Claws-Mail Raghav Gururajan
2020-09-30 10:52   ` Tobias Geerinckx-Rice via Guix-patches via
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=87ft805j27.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41111@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --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.