From: Junio C Hamano <gitster@pobox.com>
To: John Butterfield <johnb003@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Proposal: Write git subtree info to .git/config
Date: Thu, 13 Mar 2014 16:36:06 -0700 [thread overview]
Message-ID: <xmqqmwgthdsp.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAJ2ZDL+HuBCv_xJCXEBb3Pex-qt86ocEX9yu=uV+CzdvqwECDA@mail.gmail.com> (John Butterfield's message of "Thu, 13 Mar 2014 16:18:42 -0700")
John Butterfield <johnb003@gmail.com> writes:
> Has there been any talk about adding a stub for git subtrees in .git/config?
I do not think so, and that is probably for a good reason.
A subtree biding can change over time, but .git/config is about
recording information that do not change depending on what tree you
are looking at, so there is an impedance mismatch---storing that
information in .git/config is probably a wrong way to go about it.
It might help to keep track of "In this tree, the tip of that other
history is bound as a subtree at this path", which means that
information more naturally belongs to each tree, I would think.
next prev parent reply other threads:[~2014-03-13 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 23:18 Proposal: Write git subtree info to .git/config John Butterfield
2014-03-13 23:36 ` Junio C Hamano [this message]
2014-03-14 0:43 ` John Butterfield
2014-03-14 0:46 ` John Butterfield
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=xmqqmwgthdsp.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johnb003@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).