All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenther Meyer <g.meyer@signum-media.de>
To: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] [PATCH] nerdctl: renamed upstream branch master to main
Date: Fri, 18 Nov 2022 11:54:40 +0100	[thread overview]
Message-ID: <2337934.gR67lt3PR5@serenity> (raw)
In-Reply-To: <CADkTA4P8s4Eq9J-O3d7Me=0hxaowjS2exwYUhN8Nx+RbAgxUeQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

On Freitag, 18. November 2022 00:32:52 CET Bruce Ashfield wrote:
> On Thu, Nov 17, 2022 at 4:25 PM Guenther Meyer <g.meyer@signum-media.de> 
wrote:
> > On Donnerstag, 17. November 2022 19:23:08 CET Bruce Ashfield wrote:
> > > The change itself is fine, but your patch came through mangled, and it
> > > doesn't apply to the repository.
> > > 
> > > I could make the change myself, but it is probably worth sorting out
> > > which part of the patch sending chain caused the corruption.
> > 
> > Ok, what's thew problem? What can I do?
> 
> How did you relay the patch ? Was it via git-send-email or something else ?

I did a "git format-patch -1 HEAD" and pasted the result (without the header 
lines) into my MUA. As this looked similar to other patch emails, I thought, 
that would be fine.

> 
> Following my normal workflow and scripts, the patch is definitely
> garbled/line wrapped:

Ah ok, my MUA wraps lines at column 78, maybe that's the problem.
I will send the patch again.


-- 
Signum-Media Softwareentwicklung
https://www.signum-media.de
Telefon: +49 89 215 443 28

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-11-18 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 13:09 [PATCH] nerdctl: renamed upstream branch master to main Guenther Meyer
2022-11-17 18:23 ` [meta-virtualization] " Bruce Ashfield
2022-11-17 21:24   ` Guenther Meyer
2022-11-17 23:32     ` Bruce Ashfield
2022-11-18 10:54       ` Guenther Meyer [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2337934.gR67lt3PR5@serenity \
    --to=g.meyer@signum-media.de \
    --cc=meta-virtualization@lists.yoctoproject.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 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.