From: Eric Sunshine <firstname.lastname@example.org> To: Elijah Newren <email@example.com> Cc: Junio C Hamano <firstname.lastname@example.org>, Bagas Sanjaya <email@example.com>, Git Mailing List <firstname.lastname@example.org> Subject: Re: [PATCH] revisions(7): clarify that most commands take a single revision range Date: Thu, 20 May 2021 12:53:23 -0400 [thread overview] Message-ID: <CAPig+cR_rNKoY385vp3ZyQ73O1HEbysLSCMpVCG=MT9ebSNiyA@mail.gmail.com> (raw) In-Reply-To: <CABPp-BEGtrb0QjhVff57=s8-8w1CCvw9N_mAm166pzyVDcL_7g@mail.gmail.com> On Thu, May 20, 2021 at 12:45 PM Elijah Newren <email@example.com> wrote: > On Wed, May 19, 2021 at 10:03 PM Junio C Hamano <firstname.lastname@example.org> wrote: > > Well, apparently the proposed text may have failed to educate you > > about what a "revision range" is and how it works, so it is not good > > enough, so I'll postpone merging the change down further and see if > > somebody else can come up with a better description. > > > > Thanks. > > I think it's helpful and would have answered questions for users that > I've had to manually explain to folks a few times, so while it may not > be optimal, I do think your description is an improvement to the docs. > That said, it can't hurt to see if we can find out what caused Bagas' > confusion and see if we can improve it, but I wouldn't hold it up > indefinitely if no better wording comes along. For what it's worth, as a person who is far from being a revision-range expert (and who doesn't typically think about them), I found the proposed text illuminating and clearly written. I learned from it. So, I agree with Elijah that it is a good improvement to have (even if it's not perfect for every reader). : Extended LInear Jump AHead
next prev parent reply other threads:[~2021-05-20 16:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-18 11:17 Junio C Hamano 2021-05-20 2:27 ` Bagas Sanjaya 2021-05-20 4:58 ` Junio C Hamano 2021-05-20 5:02 ` Junio C Hamano 2021-05-20 5:26 ` Bagas Sanjaya 2021-05-20 16:45 ` Elijah Newren 2021-05-20 16:53 ` Eric Sunshine [this message] 2021-05-20 16:40 ` Elijah Newren 2021-05-21 19:19 ` Felipe Contreras
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='CAPig+cR_rNKoY385vp3ZyQ73O1HEbysLSCMpVCG=MT9ebSNiyA@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] revisions(7): clarify that most commands take a single revision range' \ /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
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 NNTP newsgroup(s).