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:08:23 -0800	[thread overview]
Message-ID: <7vu0bwdo08.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0601221106330.25300@iabervon.org> (Daniel Barkalow's message of "Sun, 22 Jan 2006 12:53:51 -0500 (EST)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> I think you're misunderstanding the use of the "bind" file or equivalent. 
>...
> So moving back to (A) wouldn't keep the binding point of subproject, 
> because it would rewrite bind to what it had been.

A lot better said than my version of the response.  Thanks.

> I'm going to suggest again keeping this information in the index file (but 
> not in the index data structure, so the changes to the code are only in 
> the library routines to read and write the file, and, of course, anything 
> that's actually trying to manipulate the binding locations). I started 
> working on a patch to pu to skip S_IFDIR entries from the index file when 
> building the table in memory, and that was straightforward, but I got into 
> sysadmin issues when I was going to test giving it something to skip.

I have been thinking about this one, and having read that
read-cache code I think the coding is not too involved.

My current inclination is to use the same version number (2) by
default and promote it to a new version number (3) once you add
subproject-binding information to the index file.  Then current
tools would keep working on repositories created or operated
upon with the new tools, as long as the project does not use the
new feature.

  reply	other threads:[~2006-01-22 20:08 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 [this message]
2006-01-22 20:26           ` Daniel Barkalow
2006-01-22 20:35             ` Junio C Hamano
2006-01-22 20:41       ` Junio C Hamano

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=7vu0bwdo08.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).