Mike Hommey writes:
> In typical uses of fast-import, trees are inherited from a parent
> commit. In that case, the tree_entry for the branch looks like:
> ...
> This change makes do_change_note_fanount call load_tree() whenever the
> tree_entry it is given has no tree loaded,
Sorry, I forgot the v2 in the subject.
Mike
In typical uses of fast-import, trees are inherited from a parent
commit. In that case, the tree_entry for the branch looks like:
.versions[1].sha1 = $some_sha1
.tree =
However, when trees are imported, rather than inherited, that is not the
case. One can import a tree with a filemodify
Mike Hommey writes:
> On Tue, Dec 20, 2016 at 11:34:04AM -0800, Junio C Hamano wrote:
>> Mike Hommey writes:
>>
>> > In typical uses of fast-import, trees are inherited from a parent
>> > commit. In that case, the tree_entry for the branch looks like:
>> >
On Tue, Dec 20, 2016 at 11:34:04AM -0800, Junio C Hamano wrote:
> Mike Hommey writes:
>
> > In typical uses of fast-import, trees are inherited from a parent
> > commit. In that case, the tree_entry for the branch looks like:
> > ...
> > +# Create another notes tree from the
Mike Hommey writes:
> In typical uses of fast-import, trees are inherited from a parent
> commit. In that case, the tree_entry for the branch looks like:
> ...
> +# Create another notes tree from the one above
> +cat >>input < +...
> +M 04 $(git log --no-walk --format=%T
On Mon, Dec 19, 2016 at 3:12 AM, Mike Hommey wrote:
> In typical uses of fast-import, trees are inherited from a parent
> commit. In that case, the tree_entry for the branch looks like:
>
> .versions[1].sha1 = $some_sha1
> .tree =
>
> However, when trees are imported,
In typical uses of fast-import, trees are inherited from a parent
commit. In that case, the tree_entry for the branch looks like:
.versions[1].sha1 = $some_sha1
.tree =
However, when trees are imported, rather than inherited, that is not the
case. One can import a tree with a filemodify
8 matches
Mail list logo