From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Christopher Baines <mail@cbaines.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Patchwork + automated checking and testing of patches
Date: Fri, 8 Feb 2019 19:54:33 +0100 [thread overview]
Message-ID: <20190208195433.704c93d3@alma-ubu> (raw)
In-Reply-To: <87lg2q5vwb.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On Fri, 08 Feb 2019 12:04:20 +0000
Christopher Baines <mail@cbaines.net> wrote:
> Thanks, however, one thing I've noticed is that git apply seems to be
> much more reliable at applying patches than git am. It often fails
> with "Patch is empty".
>
> I'm not sure why, it seems to work for the patches I've sent with git
> send-email, but maybe it's very particular about the formatting...
Maybe you already thought about it, but:
When I use it manually, I save the whole patch-series as an mbox-file,
including the "--cover-letter", i.e. the first email saying [0/n]. When
I then say "git am patch.mbox" it complains there is nothing in. I then
have to say "git am --skip" and it goes on automatically.
Could that also be the case with your patchwork-setup?
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2019-02-08 20:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 10:43 Patchwork + automated checking and testing of patches Christopher Baines
2018-10-31 13:34 ` Tobias Geerinckx-Rice
2018-10-31 13:53 ` Christopher Baines
2018-11-01 15:22 ` Ludovic Courtès
2018-11-01 18:55 ` Christopher Baines
2018-11-06 13:26 ` Ludovic Courtès
2018-11-06 15:13 ` Gábor Boskovits
2018-11-06 18:52 ` Ricardo Wurmus
2018-11-07 18:40 ` Christopher Baines
2018-11-07 22:00 ` Ludovic Courtès
2018-11-19 19:32 ` Christopher Baines
2018-11-22 9:07 ` Ludovic Courtès
2018-12-02 22:45 ` Chris Marusich
2018-12-03 0:51 ` Christopher Baines
2018-12-08 21:27 ` Chris Marusich
2019-02-01 12:53 ` Christopher Baines
2019-02-04 21:20 ` Ludovic Courtès
2019-02-08 12:04 ` Christopher Baines
2019-02-08 18:54 ` Björn Höfling [this message]
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=20190208195433.704c93d3@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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).