Re: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Philip Oakley
From: Mike Hommey m...@glandium.org [...] 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

Re: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Junio C Hamano
Mike Hommey m...@glandium.org 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

RE: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Randall S. Becker
On March 31, 2015 3:55 PM Philip Oakley wrote: From: Mike Hommey m...@glandium.org [...] 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

Re: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Junio C Hamano
On Tue, Mar 31, 2015 at 4:14 PM, Jonathan Nieder jrnie...@gmail.com 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

Re: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Mike Hommey
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 wasn't

Re: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Jonathan Nieder
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

Re: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Jonathan Nieder
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

Re: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Mike Hommey
On Tue, Mar 31, 2015 at 01:23:23PM -0700, Junio C Hamano wrote: Mike Hommey m...@glandium.org 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

Re: Allowing weak references to blobs and strong references to commits

2015-03-31 Thread Junio C Hamano
Mike Hommey m...@glandium.org 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