Re: What's cooking in git.git (Sep 2014, #01; Tue, 2)

On Thu, Sep 4, 2014 at 11:51 PM, Junio C Hamano [off-list ref] wrote:

Duy Nguyen [off-list ref] writes:

quoted

On Wed, Sep 3, 2014 at 5:06 AM, Junio C Hamano [off-list ref] wrote:

quoted

* nd/multiple-work-trees (2014-07-29) 39 commits

 Reroll posted, but haven't picked up yet.  How would this interact
 with rr/transaction series which is pretty much all about the refs?

Haven't checked out that topic yet. But ref changes in
multiple-work-trees are to make sure ref path construction goess
through git_path(), and some cleaning up after strbuf_git_path() is
introduced. So basically textual conflicts only.

Up to the point that is queued on 'pu', the other topic(s) still
keep the assumption that all refs are files in $GIT_DIR/refs/, and I
think I managed the textual conflicts correctly in 'pu' before.

But starting from $gmane/255476 the assumption gradually gets lifted
and eventually we may have refs and reflogs expressed in a different
backend, without these files that represent the refs at all.

I am not yet sure how this "I have $GIR_DIR/ but that is not a real
one but borrows most of the stuff from elsewhere" meshes with that
new world.

The refs/* path conversion should stay with the current filesystem
backend. How to share new backends in multiple worktrees is another
interesting problem. But I should stop saying any more until I read
this backend-struct-db  topic.
-- 
Duy