From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3] git-ptx-patches: call git in a pristine environment
Date: Mon, 18 Nov 2019 08:39:22 -0500 [thread overview]
Message-ID: <CAMwGMjyKmz_46AkiNED6G9a6vPLsvgLwiTF87iTCdEzUB9u1KA@mail.gmail.com> (raw)
In-Reply-To: <20191118093239.18000-1-rhi@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 874 bytes --]
On Mon, Nov 18, 2019 at 4:32 AM Roland Hieber <rhi@pengutronix.de> wrote:
>
> @@ -129,7 +144,7 @@ fi
> GIT_EXTRA_ARGS="$GIT_EXTRA_ARGS --summary --stat=80"
>
> cat .ptxdist/series.0 > .ptxdist/series
> -git format-patch -N $GIT_EXTRA_ARGS ${tagopt} -o .ptxdist/patches/
> ${range} | sed -e 's,^.ptxdist/patches/,,' > .ptxdist/series.auto
> +${GIT} format-patch -N $GIT_EXTRA_ARGS ${tagopt} -o .ptxdist/patches/
> ${range} | sed -e 's,^.ptxdist/patches/,,' > .ptxdist/series.auto
>
In my own ptxdist git repo, I have a patch that adds `-M` to make file
renames less verbose. Adding this should not affect the output of any patch
series maintained by ptxdist. I needed it to make less verbose some package
I was changing locally:
git format-patch -M -N $GIT_EXTRA_ARGS ${tagopt} -o .ptxdist/patches/
${range} | sed -e 's,^.ptxdist/patches/,,' > .ptxdist/series.auto
-Jon
[-- Attachment #1.2: Type: text/html, Size: 1300 bytes --]
[-- Attachment #2: Type: text/plain, Size: 92 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-11-18 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 11:31 [ptxdist] [PATCH] " Roland Hieber
2019-11-17 10:31 ` Michael Olbrich
2019-11-17 21:57 ` Roland Hieber
2019-11-18 7:18 ` Alexander Dahl
2019-11-18 9:13 ` Michael Olbrich
2019-11-18 9:21 ` [ptxdist] [PATCH v2] " Roland Hieber
2019-11-18 9:32 ` [ptxdist] [PATCH v3] " Roland Hieber
2019-11-18 13:39 ` Jon Ringle [this message]
2019-11-27 9:41 ` Roland Hieber
2019-12-05 10:15 ` Roland Hieber
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=CAMwGMjyKmz_46AkiNED6G9a6vPLsvgLwiTF87iTCdEzUB9u1KA@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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