From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Eric Sunshine <sunshine@sunshineco.com>,
Thomas Ferris Nicolaisen <tfnico@gmail.com>,
git <git@vger.kernel.org>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Nicola Paolucci <npaolucci@atlassian.com>,
Thomas Rast <tr@thomasrast.ch>, Jeff King <peff@peff.net>,
Eric Raible <raible@nextest.com>,
Emma Jane Hogbin Westby <emma@emmajane.net>,
Max Kirillov <max@max630.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
"H.Merijn Brand" <h.m.brand@xs4all.nl>,
Antoine Delaite <antoine.delaite@ensimag.grenoble-inp.fr>,
remi galan-alfonso <remi.galan-alfonso@ensimag.grenoble-inp.fr>,
remi lespinet <remi.lespinet@ensimag.grenoble-inp.fr>,
guillaume pages <guillaume.pages@ensimag.grenoble-inp.fr>,
louis--alexandre stuber
<louis--alexandre.stuber@ensimag.grenoble-inp.fr>,
karthik nayak <karthik.188@gmail.com>, Paul Tan <pyokagan@
Subject: Re: Draft of Git Rev News edition 5
Date: Wed, 08 Jul 2015 10:36:41 -0700 [thread overview]
Message-ID: <xmqqio9uy2ja.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAP8UFD1=KxcYyFfFZ++5Vty-KMv-ci8dtdo4bfX7oj_wgLOE7g@mail.gmail.com> (Christian Couder's message of "Wed, 8 Jul 2015 12:29:34 +0200")
Christian Couder <christian.couder@gmail.com> writes:
>
> I think sometimes the details might be interesting for different reasons.
> ...
> With the details, I think readers are more likely to remember the
> --merges option.
That unfortunately cuts both ways.
With too much details, the readers are more likely to skim and skip
the "--merges" buried in reams of text. Only the ones who carefully
read from cover to cover would discover and contrast the first
iteration "sed" with the second iteration "--merges", but I'd expect
that they would also be the ones who carefully read the docs and
more likely to know about "--merges" without Rev News teaching them.
Used sparingly, the details do pull interested readers in. The key
word in your message was "sometimes", I think.
next prev parent reply other threads:[~2015-07-08 17:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 11:13 Draft of Git Rev News edition 5 Christian Couder
2015-07-05 19:11 ` Eric Sunshine
2015-07-05 21:13 ` Christian Couder
2015-07-05 22:01 ` Eric Sunshine
2015-07-05 22:35 ` Thomas Ferris Nicolaisen
2015-07-05 23:12 ` Eric Sunshine
2015-07-08 7:22 ` Michael J Gruber
2015-07-08 7:43 ` Junio C Hamano
2015-07-08 10:29 ` Christian Couder
2015-07-08 13:02 ` Johannes Schindelin
2015-07-08 17:36 ` Junio C Hamano [this message]
2015-07-06 16:38 ` Junio C Hamano
2015-07-06 17:24 ` Eric Sunshine
2015-07-06 17:54 ` Junio C Hamano
2015-07-06 19:39 ` Eric Sunshine
2015-07-06 19:59 ` Christian Couder
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=xmqqio9uy2ja.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=antoine.delaite@ensimag.grenoble-inp.fr \
--cc=christian.couder@gmail.com \
--cc=emma@emmajane.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=guillaume.pages@ensimag.grenoble-inp.fr \
--cc=h.m.brand@xs4all.nl \
--cc=karthik.188@gmail.com \
--cc=louis--alexandre.stuber@ensimag.grenoble-inp.fr \
--cc=max@max630.net \
--cc=npaolucci@atlassian.com \
--cc=peff@peff.net \
--cc=raible@nextest.com \
--cc=remi.galan-alfonso@ensimag.grenoble-inp.fr \
--cc=remi.lespinet@ensimag.grenoble-inp.fr \
--cc=sunshine@sunshineco.com \
--cc=tfnico@gmail.com \
--cc=tr@thomasrast.ch \
/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.