On Tue, Mar 31, 2015 at 04:14:49PM -0700, Jonathan Nieder wrote:
> Mike Hommey wrote:
>
> > Octopus merges are limited to 16 parents.
>
> The note about this in fast-import is out of date (e.g., see
> t/t7602-merge-octopus-many.sh and v1.6.0-rc0~194, 2008-06-27). How
> about this patch?
Aha! I
On Tue, Mar 31, 2015 at 4:14 PM, Jonathan Nieder wrote:
> Mike Hommey wrote:
>
>> Octopus merges are limited to 16 parents.
>
> The note about this in fast-import is out of date (e.g., see
> t/t7602-merge-octopus-many.sh and v1.6.0-rc0~194, 2008-06-27). How
> about this patch?
Ahh, I thought we
Jonathan Nieder wrote:
> How
> about this patch?
I think I botched the wording. Here's a second try.
-- >8 --
Subject: fast-import doc: remove suggested 16-parent limit
Merges with an absurd number of parents are still a bad idea
Mike Hommey wrote:
> Octopus merges are limited to 16 parents.
The note about this in fast-import is out of date (e.g., see
t/t7602-merge-octopus-many.sh and v1.6.0-rc0~194, 2008-06-27). How
about this patch?
-- >8--
Subject: fast-import doc: remove suggested 16-parent limit
Merges with an abs
Mike Hommey writes:
> Octopus merges are limited to 16 parents.
Huh?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Mar 31, 2015 at 01:23:23PM -0700, Junio C Hamano wrote:
> Mike Hommey writes:
>
> > So I thought, since commits are already allowed in tree objects, for
> > submodules, why not add a bit to the mode that would tell git that
> > those commit object references are meant to always be there a
On March 31, 2015 3:55 PM Philip Oakley wrote:
> From: "Mike Hommey"
> [...]
> > So I thought, since commits are already allowed in tree objects, for
> > submodules, why not add a bit to the mode that would tell git that
> > those commit object references are meant to always be there aka strong
>
Mike Hommey writes:
> So I thought, since commits are already allowed in tree objects, for
> submodules, why not add a bit to the mode that would tell git that
> those commit object references are meant to always be there aka strong
> reference, as opposed to the current weak references for submo
From: "Mike Hommey"
[...]
So I thought, since commits are already allowed in tree objects, for
submodules, why not add a bit to the mode that would tell git that
those commit object references are meant to always be there aka strong
reference, as opposed to the current weak references for submo
9 matches
Mail list logo
