On Thu, Sep 20, 2018 at 11:35:23AM -0700, Stefan Beller wrote:
> > This optimization is a good one and works well, particularly when the
> > upstream repository has a relatively normal number of references. When
> > the upstream has a pathologically _large_ number of references, the
> >
On Thu, Sep 20, 2018 at 02:04:05PM -0400, Taylor Blau wrote:
> This is a series to customize Git's behavior when listing references
> from an alternate repository. It is motivated by the following example:
>
> Consider an upstream repository, a fork of it, and a local copy of that
> fork.
Hi Stefan,
On Thu, Sep 20, 2018 at 11:35:23AM -0700, Stefan Beller wrote:
> > To make the reference advertisement manageable even with a large number
> > of references, let's allow the fork to select which ones it thinks might
> > be "interesting", and only advertise those. This makes the
On Thu, Sep 20, 2018 at 11:04 AM Taylor Blau wrote:
>
> Hi,
>
> This is a series to customize Git's behavior when listing references
> from an alternate repository. It is motivated by the following example:
>
> Consider an upstream repository, a fork of it, and a local copy of that
> fork.
Hi,
This is a series to customize Git's behavior when listing references
from an alternate repository. It is motivated by the following example:
Consider an upstream repository, a fork of it, and a local copy of that
fork. Ideally, running "git pull upstream" from the local copy followed
by a
5 matches
Mail list logo