From: "Martin Ågren" <martin.agren@gmail.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2] rev-list-options.txt: start a list for `show-pulls`
Date: Tue, 26 May 2020 21:18:55 +0200 [thread overview]
Message-ID: <CAN0heSq3mv8OcFiESVhN_fZ=iChSAUQ_Js0g=bTsY5dMepkk9A@mail.gmail.com> (raw)
In-Reply-To: <4a3797f8-5169-b016-b1c4-ce544f00b34b@gmail.com>
Hi Stolee,
On Tue, 26 May 2020 at 14:24, Derrick Stolee <stolee@gmail.com> wrote:
>
> On 5/25/2020 1:06 PM, Martin Ågren wrote:
> > On Mon, 18 May 2020 at 22:22, Junio C Hamano <gitster@pobox.com> wrote:
> > @@ -671,10 +671,13 @@ important branch. Instead, the merge `N` was used to merge `R` and `X`
> > into the important branch. This commit may have information about why
> > the change `X` came to override the changes from `A` and `B` in its
> > commit message.
> > +
> > +--show-pulls::
> > + In addition to the commits shown in the default history, show
> > + each merge commit that is not TREESAME to its first parent but
> > + is TREESAME to a later parent.
> > +
> > -The `--show-pulls` option helps with both of these issues by adding more
>
> I like how you found a way to add the list item without needing to make a
> huge shift in the surrounding prose. LGTM.
Actually, I didn't see how to do it, but luckily, you did. [1] So I take
this to mean that even on re-reading your proposed text some time later,
you like it. ;-)
Martin
[1] https://lore.kernel.org/git/34870e5f-8e61-4af8-1050-43bfbe30d8f9@gmail.com/
next prev parent reply other threads:[~2020-05-26 19:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 18:52 [PATCH 0/7] Documentation fixes for v2.27.0-rc0 Martin Ågren
2020-05-17 18:52 ` [PATCH 1/7] date-formats.txt: fix list continuation Martin Ågren
2020-05-17 18:52 ` [PATCH 2/7] git-bugreport.txt: fix reference to strftime(3) Martin Ågren
2020-05-17 19:23 ` Eric Sunshine
2020-05-17 19:27 ` Martin Ågren
2020-05-18 10:54 ` Jean-Noël Avila
2020-05-18 11:15 ` Martin Ågren
2020-05-17 18:52 ` [PATCH 3/7] git-commit-graph.txt: fix grammo Martin Ågren
2020-05-18 14:46 ` Derrick Stolee
2020-05-17 18:52 ` [PATCH 4/7] git-commit-graph.txt: fix list rendering Martin Ågren
2020-05-17 18:52 ` [PATCH 5/7] git-credential.txt: use list continuation Martin Ågren
2020-05-18 23:06 ` Carlo Marcelo Arenas Belón
2020-05-17 18:52 ` [PATCH 6/7] git-sparse-checkout.txt: add missing ' Martin Ågren
2020-05-18 14:46 ` Derrick Stolee
2020-05-17 18:52 ` [PATCH 7/7] rev-list-options.txt Martin Ågren
2020-05-18 14:57 ` Derrick Stolee
2020-05-18 18:37 ` Martin Ågren
2020-05-18 20:22 ` Junio C Hamano
2020-05-25 17:06 ` [PATCH v2] rev-list-options.txt: start a list for `show-pulls` Martin Ågren
2020-05-26 12:24 ` Derrick Stolee
2020-05-26 19:18 ` Martin Ågren [this message]
2020-05-26 15:16 ` Junio C Hamano
2020-05-26 17:01 ` Derrick Stolee
2020-05-26 19:20 ` Martin Ågren
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='CAN0heSq3mv8OcFiESVhN_fZ=iChSAUQ_Js0g=bTsY5dMepkk9A@mail.gmail.com' \
--to=martin.agren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stolee@gmail.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.
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).