unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tanguy Le Carrour <tanguy@bioneland.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 37903-done@debbugs.gnu.org
Subject: [bug#37903] [PATCH v2 1/2] gnu: profanity: Update to 0.7.1.
Date: Fri, 25 Oct 2019 16:31:42 +0200	[thread overview]
Message-ID: <20191025143142.kwxy5jn5qpaszbe7@rafflesia> (raw)
In-Reply-To: <CANVeeZzPHuXqrT8JGNJ_DGBJqCNLS5AYm2mLwmCUBddu8Qz_=g@mail.gmail.com>

Hi!

Le 10/25, Mathieu Othacehe a écrit :
> > 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?

I'm sending patches with neomutt, but it turns out to be really painful
when there are more than 2 patches.
I'll configure `git send-email` asap!


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

Yeah, I have to work on that, sorry! I usually go through the log
history to find something similar, but it's not always successful!


> Thanks for your work :),

Thanks for your!

-- 
Tanguy

  reply	other threads:[~2019-10-25 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 14:10 [bug#37903] [PATCH 0/2] gnu: profanity: Update to 0.7.1 Tanguy Le Carrour
2019-10-24 14:12 ` [bug#37903] [PATCH 1/2] " Tanguy Le Carrour
2019-10-24 16:02   ` Mathieu Othacehe
2019-10-24 14:13 ` [bug#37903] [PATCH 2/2] gnu: profanity: Correct indentation Tanguy Le Carrour
2019-10-25 12:46 ` [bug#37903] [PATCH v2 1/2] gnu: profanity: Update to 0.7.1 Tanguy Le Carrour
2019-10-25 14:11   ` bug#37903: " Mathieu Othacehe
2019-10-25 14:31     ` Tanguy Le Carrour [this message]
2019-10-25 12:46 ` [bug#37903] [PATCH v2 2/2] gnu: profanity: Correct indentation Tanguy Le Carrour

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=20191025143142.kwxy5jn5qpaszbe7@rafflesia \
    --to=tanguy@bioneland.org \
    --cc=37903-done@debbugs.gnu.org \
    --cc=m.othacehe@gmail.com \
    /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).