From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: What's in git.git today
Date: Wed, 28 Dec 2005 15:32:14 -0800 [thread overview]
Message-ID: <7vbqz0ajcx.fsf@assigned-by-dhcp.cox.net> (raw)
GIT 1.0.6 was silently pushed out. Again, it has one notable
fix among minor test fixes.
- Do not mark tags fetched via --tags flag as mergeable.
This is to fix "git pull --tags"; it tried to merge all of
the tags by mistake --- it should not merge any of them.
I have verified that the patch by Gerrit to fix merge-order test
is correct, but have not got around to apply it yet.
The master branch has the following enhancements in addition to
what is in 1.0.6. I intend to have 1.1 release with them early
next year, when I come back from the new year break.
- "git clone -o branchname" to specify name of the branch used
to keep track of the upstream (Johannes).
- "core.sharedrepository" and "git init-db --shared" to help
group writable repositories (Johannes).
- IPV6 literal address in git networking protocol (Hideaki).
- "git pack-redundant" is more efficient (Lukas).
- "git describe" and associated Makefile changes to give GIT
releases a bit more descriptive names (Linus and me).
- "git checkout <treeish> <path>..." and "git checkout -- <path>..."
can be used to restore named paths even from a subdirectory.
- git-receive-pack propagates hooks' refusal to update back to
git-send-pack.
I'll be away from the network and will be back on the second
week of January. I wish everybody a happy new year.
next reply other threads:[~2005-12-28 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 23:32 Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 1:20 What's in git.git today 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=7vbqz0ajcx.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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