From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: "Jeff King" <peff@peff.net>, "Git List" <git@vger.kernel.org>
Subject: Re: name for A..B ranges?
Date: Mon, 27 Jun 2016 08:08:21 -0700 [thread overview]
Message-ID: <xmqq4m8ed5zu.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <8001594309A04A42859024BAEB8FF188@PhilipOakley> (Philip Oakley's message of "Mon, 27 Jun 2016 14:37:35 +0100")
"Philip Oakley" <philipoakley@iee.org> writes:
> ..., I was wondering
> if an alternative would be to refer to it via [use the headings of]
> it's notation, i.e. "the 'two-dot' range notation" (or 'syntax' is
> that is preferred), and the "three-dot symmetric difference notation".
That's a lot more sensible pair of headings, I would think.
> The existing explanatory text can stand as is, but they would now have
> a section for readers to find.
>
> Or should I just drop this?
I like the approach to separate them into clearly marked sections.
I primarily was reacting to the "single-sided" which nobody would
understand.
next prev parent reply other threads:[~2016-06-27 15:08 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 7:25 name for A..B ranges? Philip Oakley
2016-06-24 16:09 ` Jeff King
2016-06-24 16:44 ` Junio C Hamano
2016-06-25 13:50 ` Philip Oakley
2016-06-25 16:46 ` [PATCH 0/2] " Philip Oakley
2016-06-25 16:46 ` [PATCH 1/2] doc: use 'symmetric difference' consistently Philip Oakley
2016-06-25 16:46 ` [PATCH 2/2] doc: give headings for the two and three dot notations Philip Oakley
2016-06-25 18:47 ` [PATCH] doc: show the actual left, right, and boundary marks Philip Oakley
2016-06-30 20:25 ` [PATCH v2 0/4] Name for A..B ranges? Philip Oakley
2016-06-30 20:25 ` [PATCH v2 1/4] doc: use 'symmetric difference' consistently Philip Oakley
2016-06-30 20:25 ` [PATCH v2 2/4] doc: show the actual left, right, and boundary marks Philip Oakley
2016-06-30 20:25 ` [PATCH v2 3/4] doc: give headings for the two and three dot notations Philip Oakley
2016-06-30 20:25 ` [PATCH v2 4/4] doc: clarify that `^r1` will exclude `r1` itself Philip Oakley
2016-07-01 21:16 ` Junio C Hamano
2016-07-01 22:08 ` Philip Oakley
2016-07-01 22:14 ` Junio C Hamano
2016-07-01 23:01 ` Junio C Hamano
2016-07-10 21:17 ` Philip Oakley
2016-07-01 21:27 ` [PATCH v2 0/4] Name for A..B ranges? Junio C Hamano
2016-07-11 20:25 ` [PATCH v3 0/8] " Philip Oakley
2016-07-11 20:25 ` [PATCH v3 1/8] doc: use 'symmetric difference' consistently Philip Oakley
2016-07-11 20:25 ` [PATCH v3 2/8] doc: revisions - name the Left and Right sides Philip Oakley
2016-07-12 16:47 ` Junio C Hamano
2016-07-12 21:47 ` Philip Oakley
2016-07-11 20:25 ` [PATCH v3 3/8] doc: show the actual left, right, and boundary marks Philip Oakley
2016-07-11 20:25 ` [PATCH v3 4/8] doc: give headings for the two and three dot notations Philip Oakley
2016-07-12 13:44 ` Marc Branchaud
2016-07-12 17:04 ` Junio C Hamano
2016-07-12 22:11 ` Philip Oakley
2016-07-19 16:03 ` Jakub Narębski
2016-07-19 19:15 ` Philip Oakley
2016-07-12 21:41 ` Philip Oakley
2016-07-12 22:12 ` Jeff King
2016-07-11 20:25 ` [PATCH v3 5/8] doc: gitrevisions - use 'reachable' in page description Philip Oakley
2016-07-11 20:25 ` [PATCH v3 6/8] doc: gitrevisions - clarify 'latter case' is revision walk Philip Oakley
2016-07-11 20:25 ` [PATCH v3 7/8] doc: revisions - define `reachable` Philip Oakley
2016-07-12 13:48 ` Marc Branchaud
2016-07-12 21:44 ` Philip Oakley
2016-07-11 20:25 ` [PATCH v3 8/8] doc: revisions - clarify reachability examples Philip Oakley
2016-07-12 19:29 ` [PATCH v3 0/8] Name for A..B ranges? Junio C Hamano
2016-07-12 22:29 ` Philip Oakley
2016-07-20 21:09 ` [PATCH v4 " Philip Oakley
2016-07-20 21:10 ` [PATCH v4 1/8] doc: use 'symmetric difference' consistently Philip Oakley
2016-07-20 21:10 ` [PATCH v4 2/8] doc: revisions - name the left and right sides Philip Oakley
2016-07-20 21:10 ` [PATCH v4 3/8] doc: show the actual left, right, and boundary marks Philip Oakley
2016-07-20 21:10 ` [PATCH v4 4/8] doc: give headings for the two and three dot notations Philip Oakley
2016-07-21 14:42 ` Marc Branchaud
2016-07-21 19:54 ` Philip Oakley
2016-07-21 21:20 ` Marc Branchaud
2016-07-22 22:46 ` Junio C Hamano
2016-07-20 21:10 ` [PATCH v4 5/8] doc: gitrevisions - use 'reachable' in page description Philip Oakley
2016-07-20 21:10 ` [PATCH v4 6/8] doc: gitrevisions - clarify 'latter case' is revision walk Philip Oakley
2016-07-20 21:10 ` [PATCH v4 7/8] doc: revisions - define `reachable` Philip Oakley
2016-07-20 21:10 ` [PATCH v4 8/8] doc: revisions - clarify reachability examples Philip Oakley
2016-07-20 22:22 ` [PATCH v4 0/8] Name for A..B ranges? Junio C Hamano
2016-08-11 21:50 ` [PATCH v5 00/12] Update git revisions Philip Oakley
2016-08-11 21:50 ` [PATCH v5 01/12] doc: use 'symmetric difference' consistently Philip Oakley
2016-08-26 11:33 ` Jakub Narębski
2016-08-26 16:09 ` Junio C Hamano
2016-08-11 22:32 ` [PATCH v5 00/12] Update git revisions Philip Oakley
2016-08-12 23:45 ` [PATCH v6 " Philip Oakley
2016-08-12 23:45 ` [PATCH v6 05/12] doc: revisions: extra clarification of <rev>^! notation effects Philip Oakley
2016-08-12 23:45 ` [PATCH v6 06/12] doc: revisions: single vs multi-parent notation comparison Philip Oakley
2016-08-26 15:30 ` Jakub Narębski
2016-08-26 16:19 ` Junio C Hamano
2016-08-12 23:45 ` [PATCH v6 11/12] doc: revisions: show revision expansion in examples Philip Oakley
2016-08-12 23:45 ` [PATCH v6 12/12] doc: revisions: sort examples and fix alignment of the unchanged Philip Oakley
2016-08-15 14:30 ` [PATCH v6 00/12] Update git revisions Marc Branchaud
2016-08-15 15:00 ` Philip Oakley
2016-08-15 16:55 ` BUG: indent-with-non-tab always on (was: Re: [PATCH v6 00/12] Update git revisions) Marc Branchaud
2016-08-15 17:54 ` BUG: indent-with-non-tab always on Marc Branchaud
2016-08-15 17:06 ` [PATCH v6 00/12] Update git revisions Junio C Hamano
2016-08-31 16:22 ` Junio C Hamano
2016-08-11 23:03 ` [PATCH v5 " Philip Oakley
2016-08-11 23:03 ` [PATCH v5 01/12] doc: use 'symmetric difference' consistently Philip Oakley
2016-08-12 7:07 ` [PATCH v5 00/12] Update git revisions Philip Oakley
2016-08-12 7:07 ` [PATCH v5 01/12] doc: use 'symmetric difference' consistently Philip Oakley
2016-08-12 7:07 ` [PATCH v5 02/12] doc: revisions - name the left and right sides Philip Oakley
2016-08-12 7:07 ` [PATCH v5 03/12] doc: show the actual left, right, and boundary marks Philip Oakley
2016-08-12 7:07 ` [PATCH v5 04/12] doc: revisions: give headings for the two and three dot notations Philip Oakley
2016-08-12 7:10 ` Jeff King
2016-08-12 14:37 ` Marc Branchaud
2016-08-12 7:07 ` [PATCH v5 05/12] doc: revisions: extra clarification of <rev>^! notation effects Philip Oakley
2016-08-12 14:39 ` Marc Branchaud
2016-08-12 22:17 ` Philip Oakley
2016-08-12 7:07 ` [PATCH v5 06/12] doc: revisions: single vs multi-parent notation comparison Philip Oakley
2016-08-12 14:40 ` Marc Branchaud
2016-08-12 22:23 ` Philip Oakley
2016-08-12 7:07 ` [PATCH v5 07/12] doc: gitrevisions - use 'reachable' in page description Philip Oakley
2016-08-12 7:07 ` [PATCH v5 08/12] doc: gitrevisions - clarify 'latter case' is revision walk Philip Oakley
2016-08-12 7:07 ` [PATCH v5 09/12] doc: revisions - define `reachable` Philip Oakley
2016-08-28 13:01 ` Jakub Narębski
2016-08-29 13:21 ` Philip Oakley
2016-08-29 14:43 ` Jakub Narębski
2016-08-29 19:27 ` Philip Oakley
2016-08-12 7:07 ` [PATCH v5 10/12] doc: revisions - clarify reachability examples Philip Oakley
2016-08-12 7:07 ` [PATCH v5 11/12] doc: revisions: show revision expansion in examples Philip Oakley
2016-08-12 15:22 ` Marc Branchaud
2016-08-12 22:45 ` Philip Oakley
2016-08-12 7:07 ` [PATCH v5 12/12] doc: revisions: sort examples and fix alignment of the unchanged Philip Oakley
2016-08-12 15:28 ` [PATCH v5 00/12] Update git revisions Marc Branchaud
2016-08-12 19:20 ` Philip Oakley
2016-08-12 21:27 ` Junio C Hamano
2016-06-25 19:49 ` name for A..B ranges? Junio C Hamano
2016-06-27 13:37 ` Philip Oakley
2016-06-27 15:08 ` Junio C Hamano [this message]
2016-06-27 15:39 ` Philip Oakley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4m8ed5zu.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=philipoakley@iee.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).