From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.1.2
Date: Fri, 13 Jan 2006 20:53:29 -0800 [thread overview]
Message-ID: <7vd5ivwgty.fsf@assigned-by-dhcp.cox.net> (raw)
The latest maintenance release GIT 1.1.2 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.1.2.tar.{gz,bz2} (tarball)
RPMS/$arch/git-*-1.1.2-1.$arch.rpm (RPM)
----------------------------------------------------------------
Changes since v1.1.1 are as follows:
J. Bruce Fields:
Documentation: clarify fetch parameter descriptions.
Junio C Hamano:
update-index: work with c-quoted name
describe: do not silently ignore indescribable commits
name-rev: do not omit leading components of ref name.
show-branch: handle [] globs as well.
Documentation: git-commit -a
Documentation: git-reset - interrupted workflow.
Tom Prince:
Add git-describe to .gitignore.
----------------------------------------------------------------
These have been added to the "master" branch lately, in addition
to all of the above fixes:
Makefile: add 'strip' target.
octopus: allow criss-cross and clarify the message when it rejects.
checkout: automerge local changes while switching branches.
checkout: merge local modifications while switching branches.
git-push: avoid falling back on pushing "matching" refs.
Exec git programs without using PATH (Michal Ostrowski)
Fix the installation location.
These are still waiting their turn in the proposed updates
("pu") branch:
git-cvsimport: Add -A <author-conv-file> option (Andreas Ericsson)
convert-packs: futureproofing.
Require packfiles to follow the naming convention (preparation).
format-patch: always --mbox and show sane Date:
octopus: allow manual resolve on the last round.
Documentation: show-branch.
show-branch: make the current branch and merge commits stand out.
Disable USE_SYMLINK_HEAD by default (Pavel Roskin)
reply other threads:[~2006-01-14 4:53 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=7vd5ivwgty.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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
all inboxes | Powered by JetHome®