From: Jakub Narebski <jnareb@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: What's in git.git (stable)
Date: Sat, 16 Dec 2006 14:59:40 +0100 [thread overview]
Message-ID: <em0u4k$8hs$1@sea.gmane.org> (raw)
In-Reply-To: 7v4przfpir.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Things that need to be done to complete what have been merged to
> 'master' are:
What about discussed but not implemented moving restriction on non-head refs
from git-checkout (forbidding to checkout tags, remotes, and arbitrary
commits like HEAD~n) to git-commit (allowing commiting only to heads refs)?
Probably non-heads refs should be saved in HEAD as explicit sha1 of a
commit; this way we wont run into situation where HEAD changed under us
(because it was for example to remote branch, and we fetched since).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-16 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 21:35 What's in git.git (stable) Junio C Hamano
2006-12-16 13:59 ` Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 21:18 Junio C Hamano
2006-12-08 15:36 ` Jakub Narebski
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='em0u4k$8hs$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@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