From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] docs: minor grammar fixes for v1.7.9 release notes
Date: Thu, 26 Jan 2012 14:27:21 -0500 [thread overview]
Message-ID: <20120126192721.GA10699@sigill.intra.peff.net> (raw)
In-Reply-To: <7vwr8e2s3n.fsf@alter.siamese.dyndns.org>
On Thu, Jan 26, 2012 at 11:15:08AM -0800, Junio C Hamano wrote:
> > ... (I notice you mostly include features and not bug-fixes, which I
> > assume is to keep the list to a readable length).
>
> Actually my intention regarding fixes are:
>
> - never mention follow-up fixes to new topics merged since v1.7.8 at all;
>
> - omit mentioning trivial fixes that not many people would be bitten by
> and actually be hurt in real life (i.e. typo in an error message); and
>
> - make sure as many fixes are covered in "Fixes since v1.7.8" section.
>
> So "keep the list short" is only one-third of the motivation.
That makes sense.
I was specifically thinking of 02f7914 (remote-curl: don't pass back
fake refs), because "git push --mirror" failing is an often-reported bug
for github (and the solution is to upgrade your git client). But looking
again, I see that the fix was actually in v1.7.8.2, so it is included by
the "...and all of the fixes in the maintenance releases" text.
In general, it seems like most of our fixes go onto the maintenance
track, so the "fixes" section of a major release ends up being empty.
Which I think is a good thing.
-Peff
prev parent reply other threads:[~2012-01-26 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 22:20 [PATCH] docs: minor grammar fixes for v1.7.9 release notes Jeff King
2012-01-26 19:15 ` Junio C Hamano
2012-01-26 19:27 ` Jeff King [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=20120126192721.GA10699@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).