Hi Phillip,
On Tue, 13 Nov 2018, Phillip Wood wrote:
> On 13/11/2018 19:21, Johannes Schindelin wrote:
> > Hi Phillip,
> >
> > On Tue, 13 Nov 2018, Phillip Wood wrote:
> >
> > > Thanks for looking at this. Unfortunately using OPT_PASSTHRU_ARGV seems to
> > > break the error reporting
> > >
> >
Hi Johannes
On 13/11/2018 19:21, Johannes Schindelin wrote:
Hi Phillip,
On Tue, 13 Nov 2018, Phillip Wood wrote:
Thanks for looking at this. Unfortunately using OPT_PASSTHRU_ARGV seems to
break the error reporting
Running
bin/wrappers/git rebase --onto @ @^^ -Cbad
Gives
git
Hi Phillip,
On Tue, 13 Nov 2018, Phillip Wood wrote:
> Thanks for looking at this. Unfortunately using OPT_PASSTHRU_ARGV seems to
> break the error reporting
>
> Running
> bin/wrappers/git rebase --onto @ @^^ -Cbad
>
> Gives
> git encountered an error while preparing the patches to
Hi Johannes
Thanks for looking at this. Unfortunately using OPT_PASSTHRU_ARGV seems
to break the error reporting
Running
bin/wrappers/git rebase --onto @ @^^ -Cbad
Gives
git encountered an error while preparing the patches to replay
these revisions:
"Johannes Schindelin via GitGitGadget"
writes:
> However, there is a much better way (that I was unaware of, at the time
> when I mentored Pratik to implement these options): OPT_PASSTHRU_ARGV.
> It is intended for exactly this use case, where command-line options
> want to be parsed into a
From: Johannes Schindelin
Currently, we parse the options intended for `git am` as if we wanted to
handle them in `git rebase`, and then reconstruct them painstakingly to
define the `git_am_opt` variable.
However, there is a much better way (that I was unaware of, at the time
when I mentored
6 matches
Mail list logo
