Re: [RFD PATCH 00/32] subtree clone v2
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Aug 24, 2010, 23:09 UTC
- Message-ID
- <20100824230907.GD2376@burratino>
- In-Reply-To
- <AANLkTikipryFVf_XvvbHopWSo5Ey_mvgTevY2NAvhygQ@mail.gmail.com>
Nguyen Thai Ngoc Duy wrote:
> On Wed, Aug 25, 2010 at 8:37 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 7 quoted lines
>> is it possible to >> merge without remote contact in the boring case, when no changes have >> occured outside the narrow tree? > > That's possible (and is implemented in my series). But I guess as soon > as you do "git pull", the boring case is likely not applicable > anymore.
Makes sense.
One slightly less boring case. Is it possible to merge when the simplified history, looking only at changes outside the narrow tree, would have permitted a fast-forward?
If so, a git contributor who is only interested in Documentation/ could work on "next" between releases and keep up with "maint" and "master" longer term, without the help of a full-tree-merging machine.
More realistically, a linux-2.6 contributor only interested in one subsystem could always keep up with "master". Which would be nice.