From: Junio C Hamano <gitster@pobox.com>
To: Steven Grimm <koreth@midwinter.com>
Cc: "David Kågedal" <davidk@lysator.liu.se>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.3
Date: Sun, 02 Sep 2007 17:03:22 -0700 [thread overview]
Message-ID: <7vr6lgobsl.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <46DB4903.6060100@midwinter.com> (Steven Grimm's message of "Sun, 02 Sep 2007 16:36:35 -0700")
Steven Grimm <koreth@midwinter.com> writes:
> No argument there, of course; it needs to be documented. But maybe not
> as the very first item at the top of the release notes, which people
> might expect to be organized in a "most user-visible first" order. I
> usually expect to see general descriptions of new features and
> critical bugfixes at the top of a program's release notes, with the
> option to keep reading if I want the low-level details.
>
> Barring that, or even in addition to that, would it make sense to have
> separate "porcelain" and "plumbing" sections of the release notes?
I think that makes sense, as "most user-visible first" order
will be different what kind of "user" you are.
prev parent reply other threads:[~2007-09-03 0:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 6:31 [ANNOUNCE] GIT 1.5.3 Junio C Hamano
2007-09-02 6:34 ` A note from the maintainer Junio C Hamano
2007-09-02 6:58 ` [ANNOUNCE] GIT 1.5.3 H. Peter Anvin
2007-09-02 7:58 ` Junio C Hamano
2007-09-02 8:06 ` David Kastrup
2007-09-02 9:57 ` H. Peter Anvin
2007-09-02 17:38 ` Sean
2007-09-02 22:13 ` Junio C Hamano
2007-09-02 23:16 ` Sean
2007-09-03 0:19 ` Junio C Hamano
2007-09-03 7:51 ` H. Peter Anvin
2007-09-03 8:10 ` Junio C Hamano
2007-09-03 8:12 ` H. Peter Anvin
2007-09-03 8:35 ` Junio C Hamano
2007-09-03 8:47 ` H. Peter Anvin
2007-09-03 8:53 ` Junio C Hamano
2007-09-03 9:10 ` Junio C Hamano
2007-09-03 9:13 ` H. Peter Anvin
2007-09-03 11:32 ` Andreas Ericsson
2007-09-03 12:58 ` David Kastrup
2007-09-03 13:02 ` Andreas Ericsson
2007-09-03 13:17 ` David Kastrup
2007-09-03 7:46 ` H. Peter Anvin
2007-09-02 7:08 ` David Kastrup
2007-09-02 8:43 ` Arkadiusz Miskiewicz
2007-09-02 10:28 ` Alex Riesen
2007-09-02 10:59 ` Johannes Schindelin
2007-09-02 11:19 ` Alex Riesen
2007-09-02 12:36 ` Arkadiusz Miskiewicz
2007-09-02 15:12 ` Nicolas Vilz
2007-09-02 22:52 ` David Kågedal
2007-09-02 22:54 ` David Kågedal
2007-09-02 23:28 ` Junio C Hamano
2007-09-02 23:36 ` Steven Grimm
2007-09-03 0:03 ` 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=7vr6lgobsl.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.