On Wednesday 08 November 2017 at 05:15 pm +0100, Christian Couder wrote:
> >> +git bisect replay "$GIT_BISECT_LOG_TMP"
> >> +rm -f "$GIT_BISECT_LOG_TMP"
>
> While at it, is there a reason for the -f option above?
I was following the lead of git-bisect.sh, which has used `rm -f` for
such things ev
On Wednesday 08 November 2017 at 05:12 pm +0100, Christian Couder wrote:
> On Wed, Nov 8, 2017 at 2:59 PM, Adam Dinwoodie wrote:
> > +git bisect reset HEAD
>
> I guess that using "reset HEAD" could be cheaper than just "reset" and
> that's the reason you are using it.
Exactly that, yes. I often
>> +git bisect replay "$GIT_BISECT_LOG_TMP"
>> +rm -f "$GIT_BISECT_LOG_TMP"
While at it, is there a reason for the -f option above?
On Wed, Nov 8, 2017 at 2:59 PM, Adam Dinwoodie wrote:
> Add a short script, vaguely inspired by `git rebase --interactive`, to
> ease the process described in the `git bisect` documentation of saving
> off a bisect log, editing it, then replaying it.
Nice idea.
> Signed-off-by: Adam Dinwoodie
>
Add a short script, vaguely inspired by `git rebase --interactive`, to
ease the process described in the `git bisect` documentation of saving
off a bisect log, editing it, then replaying it.
Signed-off-by: Adam Dinwoodie
---
When I'm bisecting, I find I need to semi-regularly go back and change
5 matches
Mail list logo
