From: Edgar Toernig <froese@gmx.de>
To: linux@horizon.com
Cc: git@vger.kernel.org, linux@horizon.com
Subject: Re: Missing features in git
Date: Tue, 14 Nov 2006 19:55:59 +0100 [thread overview]
Message-ID: <20061114195559.40967ee4.froese@gmx.de> (raw)
In-Reply-To: <20061114134958.5326.qmail@science.horizon.com>
linux@horizon.com wrote:
>
> Personally, I'd prefer if the requirement that HEAD point to
> refs/heads were enforced when checking in rather than checking out.
>
> Then you could check out an arbitrary version without any of the annoyance
> above; I could "git checkout tags/foo" or even "git checkout deadbeef~3".
> I wouldn't be on a current branch (which would necessitate changing
> "git branch" output), so HEAD would simply contain an object ID directly
> rather than being a symlink/symref.
I wholeheartedly agree. For the casual user it's IMHO the most
annoying behaviour of git that you can't simply checkout an arbitrary
commit without creating a new (most of the time temporary) branch first.
Often you don't plan to change the checked out tree and giving it a
new branch name ahead is cumbersome, especially as you know that you'll
never commit into it and have to delete the branch before checking out
another tag. I would prefer this behaviour:
$ git checkout v2.6.16
... i.e. check whether it builds
$ git checkout v2.6.17
... test this one
$ git checkout v2.6.18
... change something
$ git commit
error: can't commit. not on any branch.
use "git commit -b <new-branch-name>" to commit into a new one.
$ git commit -b my-v2.6.18
next prev parent reply other threads:[~2006-11-14 18:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 13:49 Missing features in git linux
2006-11-14 14:53 ` Jakub Narebski
2006-11-14 15:47 ` Karl Hasselström
2006-11-14 17:15 ` Jakub Narebski
2006-11-14 17:36 ` Karl Hasselström
2006-11-14 17:45 ` Jakub Narebski
2006-11-14 17:49 ` Shawn Pearce
2006-11-14 18:40 ` Linus Torvalds
2006-11-14 19:37 ` Petr Baudis
2006-11-14 22:09 ` Junio C Hamano
2006-11-14 15:39 ` Karl Hasselström
2006-11-14 18:55 ` Edgar Toernig [this message]
2006-11-14 21:38 ` linux
2006-11-15 7:35 ` Karl Hasselström
2006-11-15 16:50 ` Linus Torvalds
2006-11-14 22:13 ` 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=20061114195559.40967ee4.froese@gmx.de \
--to=froese@gmx.de \
--cc=git@vger.kernel.org \
--cc=linux@horizon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.