On successful completion of a rebase in git-rebase--$backend.sh, the
$backend script cleans up on its own and exits. The cleanup routine
is however, independent of the $backend, and each $backend script
unnecessarily duplicates this work:
rm -rf $state_dir
git gc --auto
Prepare
On Fri, May 10, 2013 at 10:26 AM, Ramkumar Ramachandra
artag...@gmail.com wrote:
On successful completion of a rebase in git-rebase--$backend.sh, the
$backend script cleans up on its own and exits. The cleanup routine
is however, independent of the $backend, and each $backend script
Eric Sunshine sunsh...@sunshineco.com writes:
On Fri, May 10, 2013 at 10:26 AM, Ramkumar Ramachandra
artag...@gmail.com wrote:
On successful completion of a rebase in git-rebase--$backend.sh, the
$backend script cleans up on its own and exits. The cleanup routine
is however, independent of
Ramkumar Ramachandra artag...@gmail.com writes:
On successful completion of a rebase in git-rebase--$backend.sh, the
$backend script cleans up on its own and exits. The cleanup routine
is however, independent of the $backend, and each $backend script
unnecessarily duplicates this work:
Junio C Hamano wrote:
So it is either (1) the added code is unreachable and unexercised at
this point in the series, or
Yeah, it's (1).
Perhaps this should come a bit later in the series?
When exactly? I picked up on your suggestion to separate out the
preparation-for-$backend-to-return
5 matches
Mail list logo
