From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Samuel GROOT <samuel.groot@ensimag.grenoble-inp.fr>
Cc: Jeff King <peff@peff.net>,
Tom Russello <tom.russello@grenoble-inp.org>,
git@vger.kernel.org, erwan.mathoniere@ensimag.grenoble-inp.fr,
jordan.de-gea@ensimag.grenoble-inp.fr, gitster@pobox.com,
stefan@sevenbyte.org, jrnieder@gmail.com, rybak.a.v@gmail.com
Subject: Re: [RFC/PATCH] Formatting variables in the documentation
Date: Mon, 23 May 2016 19:57:43 +0200 [thread overview]
Message-ID: <vpq8tz0hd2g.fsf@anie.imag.fr> (raw)
In-Reply-To: <b06231ac-b100-2565-3bf7-99f268014788@ensimag.grenoble-inp.fr> (Samuel GROOT's message of "Mon, 23 May 2016 18:00:26 +0200")
Samuel GROOT <samuel.groot@ensimag.grenoble-inp.fr> writes:
> Since 2.8.3 was out recently, we could flip MAN_BOLD_LITERAL on by
> default for this cycle to shake out problems as Jeff King suggested
> [2].
2.8.3 was a bufix release, and flipping a controversial flag should
clearly not be done on a bugfix release. So, in this context, "beginning
of a cycle" means after a x.y.0 release.
Anyway, a patch enabling MAN_BOLD_LITERAL by default would need to cook
in pu and next as any other patches, so the time when the patch is sent
does not really matter.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-05-23 17:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 15:58 [RFC/PATCH] Formatting variables in the documentation Tom Russello
2016-05-18 18:15 ` Jeff King
2016-05-23 16:00 ` Samuel GROOT
2016-05-23 17:57 ` Matthieu Moy [this message]
2016-05-26 4:36 ` Jeff King
2016-05-26 16:18 ` Junio C Hamano
2016-05-26 16:23 ` Jeff King
2016-05-26 16:37 ` Junio C Hamano
2016-05-26 16:39 ` Jeff King
2016-05-31 16:20 ` [PATCH] Documentation: bold literals in man Erwan Mathoniere
2016-06-03 22:08 ` [PATCH v2] Documentation more consistent Tom Russello
2016-06-03 22:08 ` [PATCH v2 1/3] Clearer rule about formatting literals Tom Russello
2016-06-03 22:08 ` [PATCH v2 2/3] Change environment variables format Tom Russello
2016-06-03 22:08 ` [PATCH v2 3/3] Change configuration " Tom Russello
2016-06-03 22:42 ` [PATCH v2] Documentation more consistent Junio C Hamano
2016-06-06 10:09 ` [PATCH v3] " Tom Russello
2016-06-06 10:09 ` [PATCH v3 1/3] doc: clearer rule about formatting literals Tom Russello
2016-06-06 13:36 ` Matthieu Moy
2016-06-06 13:42 ` Matthieu Moy
2016-06-06 15:38 ` Tom Russello
2016-06-06 10:09 ` [PATCH v3 2/3] doc: change environment variables format Tom Russello
2016-06-06 14:08 ` Matthieu Moy
2016-06-06 16:34 ` Tom Russello
2016-06-06 10:09 ` [PATCH v3 3/3] doc: change configuration " Tom Russello
2016-06-06 14:09 ` Matthieu Moy
2016-06-07 22:35 ` [PATCH v4 0/3] Documentation more consistent Tom Russello
2016-06-07 22:35 ` [PATCH v4 1/3] doc: clearer rule about formatting literals Tom Russello
2016-06-07 22:35 ` [PATCH v4 2/3] doc: change environment variables format Tom Russello
2016-06-07 22:35 ` [PATCH v4 3/3] doc: more consistency in " Tom Russello
2016-06-08 6:26 ` Matthieu Moy
2016-06-08 17:27 ` Tom Russello
2016-06-08 6:56 ` Johannes Sixt
2016-06-08 8:12 ` Matthieu Moy
2016-06-08 17:23 ` [PATCH v4 4/3] doc: change configuration " Tom Russello
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=vpq8tz0hd2g.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=erwan.mathoniere@ensimag.grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jordan.de-gea@ensimag.grenoble-inp.fr \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=rybak.a.v@gmail.com \
--cc=samuel.groot@ensimag.grenoble-inp.fr \
--cc=stefan@sevenbyte.org \
--cc=tom.russello@grenoble-inp.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 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.