From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: What will happen to git.git in the near future
Date: Sun, 01 Oct 2006 03:16:24 -0700 [thread overview]
Message-ID: <7vd59c2vev.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7v7iztbldm.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sun, 24 Sep 2006 03:37:57 -0700")
I've tagged the tip of the master as v1.4.3-rc1 tonight, after
merging things that I listed in the message last week to be
merged from "next".
Have fun.
next prev parent reply other threads:[~2006-10-01 10:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 10:37 What will happen to git.git in the near future Junio C Hamano
2006-09-24 11:04 ` Petr Baudis
2006-09-24 16:56 ` Rene Scharfe
2006-09-24 18:33 ` Johannes Schindelin
2006-09-24 18:42 ` A Large Angry SCM
2006-10-01 10:16 ` Junio C Hamano [this message]
2006-10-01 18:38 ` Linus Torvalds
2006-10-01 18:47 ` Junio C Hamano
2006-10-01 19:56 ` Linus Torvalds
2006-10-01 18:53 ` Johannes Schindelin
2006-10-01 19:57 ` Linus Torvalds
2006-10-01 20:11 ` Johannes Schindelin
2006-10-01 20:23 ` Linus Torvalds
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=7vd59c2vev.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;
as well as URLs for NNTP newsgroup(s).