From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: (Not) What's in git.git
Date: Mon, 15 May 2006 01:46:23 -0700 [thread overview]
Message-ID: <7vves7u140.fsf@assigned-by-dhcp.cox.net> (raw)
Over the weekend everybody was busy feeding me patches, so I've
added much stuff in the "next", but without really looking deep
into each of them. It still passes the testsuite, but that
tells us more about the sparseness of the tests not the quality
of what are in the branch.
I'll review them in the coming week and have them graduate to
"master", perhaps slowly. Also what's currently in "maint" will
be tagged as 1.3.3.
I expect myself to be a bit slower for a couple of days at
least; I am still adjusting to the new development environment.
I haven't fully installed what I need nor configuired it
properly yet.
reply other threads:[~2006-05-15 8:46 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=7vves7u140.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