git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: What is in git.git
Date: Sun, 22 Jan 2006 12:41:53 -0800	[thread overview]
Message-ID: <7vbqy4c7vy.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200601220033.26321.Josef.Weidendorfer@gmx.de> (Josef Weidendorfer's message of "Sun, 22 Jan 2006 00:33:25 +0100")

Josef Weidendorfer <Josef.Weidendorfer@gmx.de> writes:

> I understand that "moving binding point of X from X/ to lib/X/" is not
> representable within the index as a simple change. Is this the main issue
> for your "against the whole git philosophy"?

No.  I meant an exposure of local branch names by recording them
in the commit object, and nothing else, by that comment.

Instead of using an extra $GIT_DIR/bind file extending what we
record in the index file is OK.  $GIT_INDEX_FILE, $GIT_DIR/HEAD,
and $GIT_DIR/bind pretty much go hand-in-hand anyway and they
_are_ local to the repository, just like branch names are, so I
do not have any problem with using local branch names in these
places, but not in a commit object (or gitlink object for that
matter).

      parent reply	other threads:[~2006-01-22 20:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21  8:03 What is in git.git Junio C Hamano
     [not found] ` <200601211524.03096.lan@ac-sw.com>
2006-01-21 10:33   ` Alexander Litvinov
2006-01-21 10:36 ` Alexander Litvinov
2006-01-21 19:37   ` Junio C Hamano
2006-01-21 22:22     ` Junio C Hamano
2006-01-21 23:33     ` Josef Weidendorfer
2006-01-22  2:44       ` Junio C Hamano
2006-01-24  1:52         ` Josef Weidendorfer
2006-01-22  3:12       ` Petr Baudis
2006-01-22 17:53       ` Daniel Barkalow
2006-01-22 20:08         ` Junio C Hamano
2006-01-22 20:26           ` Daniel Barkalow
2006-01-22 20:35             ` Junio C Hamano
2006-01-22 20:41       ` Junio C Hamano [this message]

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=7vbqy4c7vy.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    /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).