From: Junio C Hamano <junkio@cox.net>
To: jnareb@gmail.com
Cc: git@vger.kernel.org
Subject: Re: Changes between main releases of git
Date: Sat, 16 Dec 2006 13:20:05 -0800 [thread overview]
Message-ID: <7v1wmzedx6.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <em1n78$iud$1@sea.gmane.org> (Jakub Narebski's message of "Sat, 16 Dec 2006 22:07:54 +0100")
Jakub Narebski <jnareb@gmail.com> writes:
> We are now close according to Junio to git 1.5.0.
We only just started talking about v1.5.0. I would expect it to
be at least a month away, probably more. Definitely not by
Christmas nor Linus's birthday.
> I'd like to ask by the occasion what were main changes
> between main versions (main releases) of git, say starting
> from v1.0.0?
I would agree we would LOVE to have that list by the time we do
a real v1.5.0, so that should be on the TO-DO list. The
essential sources of information are:
* Previous "What's in" summaries.
* Previous "GIT v1.X.X" announcements.
* Output from this (pick the ones that are not marked with ^)
for txt in Documentation/*.txt
do
git blame v1.0.0..next -- "$txt"
done
* Output from this
git log v1.0.0..next
My time however is rather tight and I feel it is better spent on
the real development and release management. People who has
been following the git list long enough should be able to come
up with a draft to help the process.
I happen to think you are among the more qualified people.
prev parent reply other threads:[~2006-12-16 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 21:07 Changes between main releases of git Jakub Narebski
2006-12-16 21:20 ` Junio C Hamano [this message]
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=7v1wmzedx6.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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