linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Nicolas Schier <nicolas@fjasle.eu>,
	Jonathan Corbet <corbet@lwn.net>,
	Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Vipin Sharma <vipinsh@google.com>,
	linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] scripts/tags.sh: choose which directories to exclude from being indexed
Date: Mon, 12 Dec 2022 09:27:55 +1300	[thread overview]
Message-ID: <Y5Y9S0qSOAL/KHp1@mail.google.com> (raw)
In-Reply-To: <Y5VazQnY7s4+cXdM@debian.me>

On Sun, Dec 11, 2022 at 11:21:33AM +0700, Bagas Sanjaya wrote:
> On Sun, Dec 11, 2022 at 12:02:18PM +1300, Paulo Miguel Almeida wrote:
> > This patch makes it possible for the devs to specify which folders
> > they don't want to include into database as part of the
> > find_other_sources func if a makefile variable IGNOREDIRS is present,
> > otherwise the original behaviour is kept.
> 
> Better say "Add IGNOREDIRS variable, which specifies which directories
> to be ignored from indexing."
> 
> > @@ -278,6 +278,13 @@ To get all available archs you can also specify all. E.g.::
> >  
> >      $ make ALLSOURCE_ARCHS=all tags
> >  
> > +IGNOREDIRS
> > +---------------
> > +For tags/TAGS/cscope targets, you can choose which directories won't
> > +be included in the databases, separated by comma. E.g.:
> > +
> > +    $ make IGNOREDIRS=drivers/gpu/drm/radeon,tools cscope
> > +
> 
> Use two-colon syntax (::) for code block above to be consistent with
> other code blocks.
> 
> Thanks. 
> 
> -- 
> An old man doll... just what I always wanted! - Clara

Hi Bagas,

thanks for taking the time to review this patch. I will make the changes
that you've pointed out.

thanks!

- Paulo A,


  reply	other threads:[~2022-12-11 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Y5T66yWNVAZNIaJ0@mail.google.com>
2022-12-10 23:02 ` [PATCH v2] scripts/tags.sh: choose which directories to exclude from being indexed Paulo Miguel Almeida
2022-12-11  4:21   ` Bagas Sanjaya
2022-12-11 20:27     ` Paulo Miguel Almeida [this message]
2022-12-12 21:27   ` Vipin Sharma
2022-12-12 21:59     ` Paulo Miguel Almeida
2022-12-12 22:32       ` Vipin Sharma
2022-12-13  2:03         ` Paulo Miguel Almeida
2022-12-13 20:26           ` [PATCH v3] " Paulo Miguel Almeida
2022-12-14 17:40             ` Vipin Sharma

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=Y5Y9S0qSOAL/KHp1@mail.google.com \
    --to=paulo.miguel.almeida.rodenas@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=vipinsh@google.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 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).