From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Broken patches
Date: Wed, 11 Oct 2017 14:50:03 +0100 [thread overview]
Message-ID: <1507729803.4045.77.camel@ipfire.org> (raw)
In-Reply-To: <20171011154805.6936166f.peter.mueller@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
Hi,
did you use git send-email or did you copy and paste them into your MUA?
-Michael
On Wed, 2017-10-11 at 15:48 +0200, Peter Müller wrote:
> Hello Michael,
>
> thanks for notifying me about these broken patches.
> I have absolutely no idea why this is happening - git does not
> seem to like me. :-(
>
> Working on this...
>
> Best regards,
> Peter Müller
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-11 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 13:48 Peter Müller
2017-10-11 13:50 ` Michael Tremer [this message]
2017-10-11 14:01 ` Peter Müller
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=1507729803.4045.77.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox