From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: GIT 0.99.9e
Date: Sun, 06 Nov 2005 21:43:19 -0800 [thread overview]
Message-ID: <7v64r5t3m0.fsf@assigned-by-dhcp.cox.net> (raw)
GIT 0.99.9e maintenance release is found at the usual places:
RPM, tarballs, and deb:
http://www.kernel.org/pub/software/scm/git/
With git, fetch maint branch from
git://git.kernel.org/pub/scm/git/git.git/
It contains everything from the master branch. Since we seem to
be shelving the separate git binary directory idea indefinitely,
what we have here is pretty much what will be in 1.0, from the
source code POV.
- http-push seems to still have a bug or two but that is to be
expected for any new code, and I am reasonably sure it can be
ironed out; preferably before 1.0 but it is not a
showstopper.
- I've done the initial round of package splitting for Debian
side myself, but it probably needs proofreading and fixing by
experienced Debian person. Similar RPM package splitting
that parallels the above is needed. Although it is not an
absolute requirement for my sources to have perfect binary
packaging support (I am just an upstream for binary
packagers), it is certainly desirable to have RPM specs and
debian/ files in a presentable shape for 1.0.
- I still need to go over the tutorial and core-ish
documentation once for consistency checks.
Changes since 0.99.9d are:
Johannes Schindelin:
Allow GIT_DIR to be an absolute path
http-fetch: do not use curl_message after releasing it
Jon Loeliger:
Refactor merge strategies into separate includable file.
Junio C Hamano:
test: t4102-apply-rename fails with strict umask (Peter Baumann).
git-format-patch: silly typo fix.
Documentation: pull/clone ref mapping clarification (Josef Weidendorfer).
git-fetch: fail if specified refspec does not match remote.
Simplify CFLAGS/DEFINES in Makefile
Package split: Debian.
Install asciidoc sources as well.
Further Debian split fixes.
Debian: test build.
Merge in http-push first stage.
Document expat dependency when using http-push.
ls-files: --others should not say unmerged paths are unknown.
git-status: do not mark unmerged paths as committable.
Set up remotes/origin to track all remote branches.
Nick Hengeveld:
Add support for pushing to a remote repository using HTTP/DAV
Verify remote packs, speed up pending request queue
Support remote references with slashes in their names
Improve lock handling
Refresh the remote lock if it is about to expire
Paul Collins:
http-push.c: include with angle bracket, not dq.
Randal L. Schwartz:
Use fink/darwinport paths for OSX
next reply other threads:[~2005-11-07 5:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 5:43 Junio C Hamano [this message]
2005-11-07 11:43 ` GIT 0.99.9e Johannes Schindelin
2005-11-07 15:47 ` Nick Hengeveld
2005-11-07 17:08 ` H. Peter Anvin
2005-11-07 19:02 ` Ingo Oeser
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=7v64r5t3m0.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;
as well as URLs for NNTP newsgroup(s).