public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: Error in posix_spawn(3) man page
Date: Mon, 10 Jan 2022 09:58:19 +0100	[thread overview]
Message-ID: <Ydv1K2U6f82XWWHx@calimero.vinschen.de> (raw)
In-Reply-To: <CAAHpriMQOt6N7H5tBvZbz-fCWf_sRi_ci-De+zF=Akd4pDS4sw@mail.gmail.com>

On Jan  7 20:30, Keith Thompson wrote:
> On Fri, Jan 7, 2022 at 4:01 PM Keith Thompson
> <Keith.S.Thompson@gmail.com> wrote:
> > The problem was that I had diff.noprefix=true in my $HOME/.gitconfig.
> > It caused `git format-patch` to omit the `a/` and `b/` prefixes, and `git am`
> > doesn't appear to have any way to consume a patch with those prefixes missing.
> >
> > I've attached an updated patch that should apply cleanly.
> >
> > (I'd argue that this is a git bug, but of course this isn't the place
> > to report it.)
> 
> I submitted a Git bug report. The response:
> ] The -p<num> flag controls how many segments `git am` or `git apply`
> ] removes. The default is -p1. `git am -p0` should apply the patch
> ] correctly.
> 
> The "-p<n>" option to "git am" is mentioned in the git-am(1) man page,
> but explained only by reference to git-apply(1), so it's easy to miss
> (I certainly did).
> 
> My original patch could have been applied with `git am -p0`. I hope
> this is useful if you receive any future patches with the same issue.

D'oh, thanks!  I pushed your patch.


Corinna


      reply	other threads:[~2022-01-10  8:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  3:24 Keith Thompson
     [not found] ` <DM3P110MB0522D24ED83275B9EC07839A9A449@DM3P110MB0522.NAMP110.PROD.OUTLOOK.COM>
2021-12-29 16:59   ` Fw: " C Howland
2022-01-05 11:46 ` Corinna Vinschen
2022-01-05 21:39   ` Keith Thompson
2022-01-07  9:32     ` Corinna Vinschen
2022-01-07 19:03       ` Brian Inglis
2022-01-07 20:02       ` Keith Thompson
2022-01-08  0:01       ` Keith Thompson
2022-01-08  4:30         ` Keith Thompson
2022-01-10  8:58           ` Corinna Vinschen [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=Ydv1K2U6f82XWWHx@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=newlib@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).