From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Many things pushed out to 'master'
Date: Mon, 03 Dec 2007 02:00:02 -0800 [thread overview]
Message-ID: <7vbq98jdy5.fsf_-_@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vabosse23.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 02 Dec 2007 18:32:52 -0800")
I've merged a handful topics that have been cooking in 'next' to
'master'. Except for a few big topics still in 'next', this brings the
tip of 'master' much closer to what will become 1.5.4.
As always has been promised, the tip of 'master' is designed to be more
stable than any released version without introducing regression, and we
need to test how true that is from time to time ;-).
Please keep the fixes flowing. The next batch will be "commit in C" and
"add --patch" series.
next prev parent reply other threads:[~2007-12-03 10:00 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 22:04 v1.5.4 plans Junio C Hamano
2007-12-02 22:33 ` Jakub Narebski
2007-12-02 22:41 ` Junio C Hamano
2007-12-02 23:39 ` David Symonds
2007-12-03 2:32 ` Junio C Hamano
2007-12-03 10:00 ` Junio C Hamano [this message]
2007-12-03 11:12 ` Many things pushed out to 'master' Johannes Schindelin
2007-12-03 18:19 ` Junio C Hamano
2007-12-03 18:39 ` Johannes Schindelin
2007-12-03 20:58 ` Junio C Hamano
2007-12-03 22:44 ` [PATCH] fast-export: rename the signed tag mode 'ignore' to 'verbatim' Johannes Schindelin
2007-12-03 22:56 ` Johannes Schindelin
2007-12-03 9:06 ` [PATCH] Fix quote_path when called with negative length Pierre Habouzit
2007-12-03 17:18 ` Jeff King
2007-12-03 18:06 ` v1.5.4 plans Nicolas Pitre
2007-12-03 21:23 ` Junio C Hamano
2007-12-14 3:32 ` [PATCH] provide advance warning of some future pack default changes Nicolas Pitre
2007-12-14 5:19 ` Junio C Hamano
2007-12-14 13:14 ` Nicolas Pitre
2007-12-14 12:45 ` Jakub Narebski
2007-12-14 13:38 ` Nicolas Pitre
2007-12-14 21:52 ` Joel Becker
2007-12-14 22:34 ` Nicolas Pitre
2007-12-14 22:39 ` Joel Becker
2007-12-14 22:46 ` Nicolas Pitre
2007-12-15 0:42 ` Joel Becker
2007-12-15 1:08 ` Nicolas Pitre
2007-12-15 1:21 ` Johannes Schindelin
2007-12-15 1:43 ` Junio C Hamano
2007-12-15 2:23 ` Nicolas Pitre
2007-12-17 20:09 ` Joel Becker
2007-12-17 20:41 ` Nicolas Pitre
2007-12-17 21:13 ` Joel Becker
2007-12-17 21:30 ` J. Bruce Fields
2007-12-17 21:52 ` Nicolas Pitre
2007-12-17 21:57 ` J. Bruce Fields
2007-12-17 22:15 ` Nicolas Pitre
2007-12-17 22:17 ` Junio C Hamano
2007-12-17 22:30 ` J. Bruce Fields
2007-12-17 22:55 ` Junio C Hamano
2007-12-18 0:04 ` J. Bruce Fields
2007-12-17 23:13 ` Nicolas Pitre
2007-12-17 21:16 ` Junio C Hamano
2007-12-17 21:45 ` Nicolas Pitre
2007-12-18 0:41 ` Junio C Hamano
2007-12-18 2:23 ` Mark Fasheh
2007-12-18 3:23 ` Nicolas Pitre
2007-12-18 3:52 ` Martin Langhoff
2007-12-18 4:09 ` Nicolas Pitre
2007-12-18 5:01 ` Junio C Hamano
2007-12-18 9:24 ` Jakub Narebski
2007-12-18 12:03 ` Johannes Schindelin
2007-12-18 14:16 ` Nicolas Pitre
2007-12-18 11:11 ` Jeff King
2007-12-18 12:06 ` Johannes Schindelin
2007-12-18 12:48 ` Jeff King
2007-12-18 13:30 ` Johannes Schindelin
2007-12-18 19:30 ` Jeff King
2007-12-18 20:12 ` Nicolas Pitre
2007-12-18 13:47 ` Jakub Narebski
2007-12-18 20:24 ` Junio C Hamano
2007-12-18 2:15 ` Mark Fasheh
2007-12-18 3:34 ` Nicolas Pitre
2007-12-04 0:48 ` v1.5.4 plans Russell
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vbq98jdy5.fsf_-_@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).