git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Jan Hudec <bulb@ucw.cz>, David Woodhouse <dwmw2@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Theodore Tso <tytso@mit.edu>,
	Andy Parkins <andyparkins@gmail.com>,
	git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: mtimes of working files
Date: Sat, 14 Jul 2007 21:46:47 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707142135090.14596@iabervon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707142331380.14090@beast.quantumfyre.co.uk>

On Sat, 14 Jul 2007, Julian Phillips wrote:

> On Sun, 15 Jul 2007, Jan Hudec wrote:
> 
> > It would be IMHO possible to symlink all the stuff in .git except HEAD and
> > index, except for one problem. This is if you have two checkouts from the
> > same branch and check out of them, the other one needs to know, that it's
> > head should now be detached to stay where it was.
> 
> You basically just described what the git-new-workdir script in
> contrib/workdir does ... it doesn't address the issue of reference updating.

That's where keeping the index's parents in the index would help. Various 
people have implemented it at various times, but it's never quite become 
sufficiently important to people to have the correct behavior worked out 
and put into mainline. IIRC, not too long ago Junio had an implementation 
in pu, but ended up dropping it because almost nobody would see a difference, 
and the people who did see a difference only had it interfere with what 
they were trying to do.

	-Daniel
*This .sig left intentionally blank*

  reply	other threads:[~2007-07-15  1:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 15:08 mtimes of working files Yakov Lerner
2007-07-11 18:05 ` Johannes Schindelin
2007-07-11 18:36   ` Yakov Lerner
2007-07-11 18:42     ` Johannes Schindelin
2007-07-11 20:26       ` Jan Hudec
2007-07-12  7:57         ` Andy Parkins
2007-07-12 17:27           ` David Woodhouse
2007-07-13  0:37             ` Theodore Tso
2007-07-13 23:00               ` David Woodhouse
2007-07-13 23:18                 ` Linus Torvalds
2007-07-13 23:46                   ` David Woodhouse
2007-07-14  0:10                     ` Linus Torvalds
2007-07-14  0:36                       ` David Woodhouse
2007-07-14  0:44                         ` J. Bruce Fields
2007-07-14  0:49                           ` David Woodhouse
2007-07-14  1:29                             ` Jakub Narebski
2007-07-14 13:23                             ` Robin Rosenberg
2007-07-14 13:09                     ` Julian Phillips
2007-07-14 22:22                     ` Jan Hudec
2007-07-14 22:36                       ` Julian Phillips
2007-07-15  1:46                         ` Daniel Barkalow [this message]
2007-07-12  6:26       ` Eric Wong
2007-07-12 13:05         ` Randal L. Schwartz
2007-07-12 18:25           ` Eric Wong

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=Pine.LNX.4.64.0707142135090.14596@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=andyparkins@gmail.com \
    --cc=bulb@ucw.cz \
    --cc=dwmw2@infradead.org \
    --cc=git@vger.kernel.org \
    --cc=julian@quantumfyre.co.uk \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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).