Re: Bootstrapping into git, commit gripes at me

From: Matthias Urlichs <smurf@smurf.noris.de>
Date: Jul 12, 2005, 16:29 UTC
Message-ID: <pan.2005.07.12.16.29.24.715453@smurf.noris.de>
In-Reply-To: <7vy88c5r4w.fsf@assigned-by-dhcp.cox.net>

Hi, Junio C Hamano wrote:

Show 6 quoted lines

> Having said that, I do like the concept of keeping track of
> "which development line are we on, and what's most recent in
> it".  The way I read your description of cg-seek, you currently
> have that information is either in .git/head-name and
> .git/refs/heads/<head-name> pair (when .git/head-name exists),
> or .git/HEAD.

Personally, I'd rather have as few invariants as possible, so that various Porcelains can agree on semantics.

What I would expect from a sane .git tree is that
* .git/HEAD contains the commit that is currently checked out.
* If HEAD is not a symlink, then switching to a branch HEAD is not a part
  of should emit a warning.
  ("fsck to find the dangling commits" is not an answer ;-)

Ideas like
* remember the branch to un-seek back to
or
* treat HEAD as read-only when there's a seek active

seem to be optional / Porcelain-specific.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
"We'll strategically withdraw to previously prepared position."
"Who prepared them?"
"we'll prepare them when we get there."
		-- Terry Pratchett (Reaper Man)