All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>, Ronnie Sahlberg <sahlberg@google.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: What's cooking in git.git (Sep 2014, #01; Tue, 2)
Date: Thu, 04 Sep 2014 09:51:35 -0700	[thread overview]
Message-ID: <xmqqtx4nuy5k.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACsJy8C_=aNX9LT2V_zhw++tC22C5SDfwbpTS=juONMxwcV9pA@mail.gmail.com> (Duy Nguyen's message of "Thu, 4 Sep 2014 20:46:53 +0700")

Duy Nguyen <pclouds@gmail.com> writes:

> On Wed, Sep 3, 2014 at 5:06 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> * 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.

  reply	other threads:[~2014-09-04 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 22:06 What's cooking in git.git (Sep 2014, #01; Tue, 2) Junio C Hamano
2014-09-03  6:27 ` Johannes Sixt
2014-09-03 18:45   ` Torsten Bögershausen
2014-09-03 19:18   ` Junio C Hamano
2014-09-03 19:30     ` Keller, Jacob E
2014-09-04 13:46 ` Duy Nguyen
2014-09-04 16:51   ` Junio C Hamano [this message]
2014-09-04 17:14     ` Junio C Hamano
2014-09-04 17:25       ` Junio C Hamano
2014-09-05  1:18       ` Duy Nguyen
2014-09-05  0:47     ` Duy Nguyen
2015-03-26 13:46 ` Tommy38

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqtx4nuy5k.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=pclouds@gmail.com \
    --cc=sahlberg@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.