From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3] git-ptx-patches: call git in a pristine environment
Date: Thu, 5 Dec 2019 11:15:40 +0100 [thread overview]
Message-ID: <20191205101540.rkbtrmp6pqitnuv6@pengutronix.de> (raw)
In-Reply-To: <20191127094120.4fecemepjs5pxdsm@pengutronix.de>
On Wed, Nov 27, 2019 at 10:41:20AM +0100, Roland Hieber wrote:
> On Mon, Nov 18, 2019 at 08:39:22AM -0500, Jon Ringle wrote:
> > 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
>
> Does this do the right thing then even when the patches are not applied
> by git during the extract stage?
In any case, adding -M to format-patch is trying to solve a different problem
than what I'm doing with my patch here, so it should be a separate patch.
Any more comments on this patch?
- Roland
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-12-05 10:15 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
2019-11-27 9:41 ` Roland Hieber
2019-12-05 10:15 ` Roland Hieber [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=20191205101540.rkbtrmp6pqitnuv6@pengutronix.de \
--to=rhi@pengutronix.de \
--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