On Thu, Jun 01, 2017 at 01:15:57PM +0200, Johannes Schindelin wrote:
> On Wed, 31 May 2017, Jeff King wrote:
>
> > I'm generally in favor of progress meters, though it does seem a little
> > funny to me that we'd need one on format-patch.
>
> When working with huge repositories with a large
Hi Peff,
On Wed, 31 May 2017, Jeff King wrote:
> I'm generally in favor of progress meters, though it does seem a little
> funny to me that we'd need one on format-patch.
When working with huge repositories with a large number of branches, it is
all too easy to pick the wrong branch to rebase
Jeff King writes:
> As I said above, I think I'd prefer it to require "--progress", as
> format-patch is quite often used as plumbing.
Yes, that sounds sensible.
Initially, my reaction was "Why do we even need --progress for
format-patch, when it gives one-line per patch output
On Wed, May 31, 2017 at 08:04:26AM -0700, Kevin Willford wrote:
> When generating patches for the rebase command if the user does
> not realize the branch they are rebasing onto is thousands of
> commits different there is no progress indication after initial
> rewinding message.
>
> This patch
om>; Kevin
> Willford <kewi...@microsoft.com>
> Subject: Re: [PATCH 1/2] format-patch: have progress option while
> generating patches
>
> On Wed, May 31, 2017 at 8:04 AM, Kevin Willford <kcwillf...@gmail.com>
> wrote:
> > When generating patches
On Wed, May 31, 2017 at 8:04 AM, Kevin Willford wrote:
> When generating patches for the rebase command if the user does
> not realize the branch they are rebasing onto is thousands of
> commits different there is no progress indication after initial
> rewinding message.
>
>
6 matches
Mail list logo