From: "Philip Oakley" <philipoakley@iee.org>
To: "Junio C Hamano" <gitster@pobox.com>, <git@vger.kernel.org>
Cc: "Marc Branchaud" <marcnarc@xiplink.com>,
"Jeff King" <peff@peff.net>, "Jakub Narebski" <jnareb@gmail.com>
Subject: Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)
Date: Fri, 5 Aug 2016 00:10:03 +0100 [thread overview]
Message-ID: <62BF22F2A6654F5DBB84660A7E32CFBD@PhilipOakley> (raw)
In-Reply-To: xmqqshukyxqw.fsf@gitster.mtv.corp.google.com
From: "Junio C Hamano" <gitster@pobox.com>
>
> * po/range-doc (2016-07-20) 8 commits
> - doc: revisions - clarify reachability examples
> - doc: revisions - define `reachable`
> - doc: gitrevisions - clarify 'latter case' is revision walk
> - doc: gitrevisions - use 'reachable' in page description
> - doc: give headings for the two and three dot notations
> - doc: show the actual left, right, and boundary marks
> - doc: revisions - name the left and right sides
> - doc: use 'symmetric difference' consistently
>
> Clarify various ways to specify the "revision ranges" in the
> documentation.
>
> Updates in 4/8 ("give headings") is reported to break formatting?
> cf. <57913C97.1030001@xiplink.com>
>
>
Just to say I haven't forgotten.
The format breakage was analysed by Jeff (12 July 2016 23:12) and looks to
be internal to the man viewer.
There's still a suggestion surrounding one of the headings to sort (which
has gone around in circles;-).
Also I now think I have a sensible idea for the <rev>^@/! examples (i.e. use
the Loeliger illustration) - that'd make if 9 in the series (was originally
2).
Plus ensure all comments across V1-4 have been attended to (including yours
of 12 July 2016 18:04).
--
Philip
next prev parent reply other threads:[~2016-08-04 23:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 22:28 What's cooking in git.git (Aug 2016, #02; Thu, 4) Junio C Hamano
2016-08-04 22:56 ` Mike Hommey
2016-08-04 23:32 ` Junio C Hamano
2016-08-04 23:39 ` Mike Hommey
2016-08-08 6:48 ` Torsten Bögershausen
2016-08-08 6:50 ` Mike Hommey
2016-08-04 23:10 ` Philip Oakley [this message]
2016-08-04 23:32 ` Junio C Hamano
2016-08-04 23:34 ` Eric Wong
2016-08-05 6:25 ` Junio C Hamano
2016-08-05 7:45 ` Jeff King
2016-08-05 8:02 ` Eric Wong
2016-08-05 8:11 ` Jeff King
2016-08-05 8:26 ` Eric Wong
2016-08-05 8:34 ` Jeff King
2016-08-05 9:14 ` Eric Wong
2016-08-07 9:06 ` Johannes Schindelin
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=62BF22F2A6654F5DBB84660A7E32CFBD@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=marcnarc@xiplink.com \
--cc=peff@peff.net \
/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