From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: What's new in GIT today
Date: Mon, 03 Oct 2005 19:20:21 -0700 [thread overview]
Message-ID: <7virwehvkq.fsf@assigned-by-dhcp.cox.net> (raw)
GIT 0.99.8a is found in the usual places. It contains the
following fixes:
- Documentation formatting updates, by Jonas Fonseca.
- Fredrik Kuivinen fixed git-merge to stash away the original
tree state correctly when using more than one merge
strategy. The same commit also adds support for baseless
merges.
- 'git repack' can get confused if the tree had a funny
filename.
- Specifying object name with just a short SHA1 prefix sort-of
worked, but did not do the right thing when ambiguities
existed between packed and unpacked objects; after thinking
about it more, I realize that the fixed code still misses
some ambiguities, but it is a bit better than before.
On the "master" branch front:
- All of the above, plus the missing fix for SHA1 prefix
uniqueness check (to be included in 0.99.8b).
- Cygwin port by H. Peter Anvin.
- Option parsing in 'git pull' was buggy and could not
recognize the following sequence:
$ git fetch http://kernel.org/pub/scm/git/git-cygwin.git/
$ git pull -a . fixes pull
to fetch a remote and use that head along with two other
local heads to create a four-head Octopus.
reply other threads:[~2005-10-04 2:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7virwehvkq.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