All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Quentin Schulz" <foss@0leil.net>
To: docs@lists.yoctoproject.org,
	Michael Opdenacker <michael.opdenacker@bootlin.com>,
	Quentin Schulz <quentin.schulz@streamunlimited.com>
Subject: Re: [docs] [PATCH] manuals: simplify colon usage
Date: Thu, 15 Apr 2021 18:14:52 +0000	[thread overview]
Message-ID: <7BD96963-1AFA-4FD8-9805-281EEE50C8C0@0leil.net> (raw)
In-Reply-To: <a45556a5-78f8-1c3e-ae36-335636981efa@bootlin.com>



On April 15, 2021 5:10:04 PM UTC, Michael Opdenacker <michael.opdenacker@bootlin.com> wrote:
>Hi Quentin
>
>On 4/15/21 6:55 PM, Quentin Schulz wrote:
>> On Thu, Apr 15, 2021 at 06:14:33PM +0200, Michael Opdenacker wrote:
>>> On 4/15/21 6:09 PM, Michael Opdenacker wrote:
>>>> - This replaces instances of ": ::" by "::", which
>>>>   generates identical HTML output
>> Could you explain how you did the changes? I'm pretty sure you are not
>> crazy enough to do all those changes by hand :)
>
>
>Yes, I am!
>I was using:
>
>git grep -Ovi ": ::"
>
>This takes at most a few minutes to go through all the matches and
>substitute them all in the same way. Actually, when the number of
>changes is still not prohibitive such as here, my personal preference is
>to check each instance before making the substitution (just alternating
>between "n" and "." in vim) to make sure it's not a special case that
>would be different. Otherwise, I'd have to inspect each line in the
>generated patch which would be an equivalent effort, wouldn't it?
>

I would craft a command and then check the patch. But honestly, I don't know if it's any better. It's anyway time consuming.

>By the way, which remaining occurrences did you find?
>

I used ag -R ":\n\s*::" to find them. It'll probably work fine with git grep instead of ag. Or :%s/:\n\s*::/::/gc in vim I guess?

Cheers,
Quentin

  reply	other threads:[~2021-04-15 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167613DD803B4636.18329@lists.yoctoproject.org>
2021-04-15 16:14 ` [docs] [PATCH] manuals: simplify colon usage Michael Opdenacker
2021-04-15 16:53   ` Quentin Schulz
2021-04-15 16:55   ` Quentin Schulz
2021-04-15 17:10     ` Michael Opdenacker
2021-04-15 18:14       ` Quentin Schulz [this message]
2021-04-15 18:28         ` Michael Opdenacker

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=7BD96963-1AFA-4FD8-9805-281EEE50C8C0@0leil.net \
    --to=foss@0leil.net \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    --cc=quentin.schulz@streamunlimited.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.
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.