GNU bug report logs - #37903
[PATCH 0/2] gnu: profanity: Update to 0.7.1.

Previous Next

Package: guix-patches;

Reported by: Tanguy Le Carrour <tanguy <at> bioneland.org>

Date: Thu, 24 Oct 2019 14:11:01 UTC

Severity: normal

Tags: patch

Done: Mathieu Othacehe <m.othacehe <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#37903: closed ([PATCH 0/2] gnu: profanity: Update to 0.7.1.)
Date: Fri, 25 Oct 2019 14:13:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Fri, 25 Oct 2019 16:11:45 +0200
with message-id <CANVeeZzPHuXqrT8JGNJ_DGBJqCNLS5AYm2mLwmCUBddu8Qz_=g <at> mail.gmail.com>
and subject line Re: [bug#37903] [PATCH v2 1/2] gnu: profanity: Update to 0.7.1.
has caused the debbugs.gnu.org bug report #37903,
regarding [PATCH 0/2] gnu: profanity: Update to 0.7.1.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
37903: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=37903
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Tanguy Le Carrour <tanguy <at> bioneland.org>
To: Guix <guix-patches <at> gnu.org>
Subject: [PATCH 0/2] gnu: profanity: Update to 0.7.1.
Date: Thu, 24 Oct 2019 16:10:00 +0200

[Message part 3 (message/rfc822, inline)]
From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Tanguy Le Carrour <tanguy <at> bioneland.org>
Cc: 37903-done <at> debbugs.gnu.org
Subject: Re: [bug#37903] [PATCH v2 1/2] gnu: profanity: Update to 0.7.1.
Date: Fri, 25 Oct 2019 16:11:45 +0200
Hello Tanguy,

> Sorry, I thought I had pull the latest master!
> I also added something about the source URL in the commit message.

The patch applying issue seems to come from an encoding issue. Could you
check the configuration of your mailer, or use git send-email instead?

You can convince yourself of the issue by trying to apply your patch,
from your email, using git am command.

I also edited the commit message of the first patch to follow commit log
conventions.

Thanks for your work :),

Mathieu


This bug report was last modified 5 years and 270 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.