From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Missing features in git
Date: Tue, 14 Nov 2006 15:53:18 +0100 [thread overview]
Message-ID: <ejcl6l$bo0$1@sea.gmane.org> (raw)
In-Reply-To: 20061114134958.5326.qmail@science.horizon.com
linux@horizon.com wrote:
> One thing I noticed is that with ref logs, you've just re-invented the
> CVS problem of associating history with a name. If you want to rename
> a branch (say, from "mischacks" to something suitable for publication),
> do you rename the log or not? It's a less virulent form, but it seems
> like the same disease.
Well, it would be nice to have command to rename branches (with its reflog)
and to rename tags (even in their packed format).
[...]
> 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.
And what would happen if you want to checkout other branch? Where the ID
in the HEAD would go to? HEAD just _has_ to be reference to _branch_.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-14 14:53 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 [this message]
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
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='ejcl6l$bo0$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).