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 wrote:
> >
> > >
> > > @@ -129,7 +144,7 @@ fi
> > > GIT_EXTRA_ARGS="$GIT_EXTRA_ARGS --summary --stat=80"
> > >
> > >
On Mon, Nov 18, 2019 at 08:39:22AM -0500, Jon Ringle wrote:
> On Mon, Nov 18, 2019 at 4:32 AM Roland Hieber 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
On Mon, Nov 18, 2019 at 4:32 AM Roland Hieber 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/,,'
The behaviour of git-format-patch can be customized through user-defined
variables from the environment or from the user's .gitconfig, like
custom regexes for function context in diff hunk headers, or different
cleanup options. These things can lead to fuzz in generated patches
which cannot easily
