From: Julia Lawall <julia.lawall@inria.fr>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Wolfram Sang <wsa@kernel.org>, cocci@inria.fr
Subject: Re: [cocci] new version 1.2
Date: Tue, 16 Apr 2024 18:07:28 +0200 (CEST) [thread overview]
Message-ID: <762b29b1-c2ba-e9e6-1054-5d4bf54b6843@inria.fr> (raw)
In-Reply-To: <5rctzuo7ynserxtyhsikkc4zhglcdqoysnt4kd3odethcv6f2o@2crrvxx6bx2b>
On Tue, 16 Apr 2024, Wolfram Sang wrote:
>
> > I can just try it, but what is CDPATH for?
>
> CDPATH is a list of directories for the 'cd' command. I have '.' and
> "$HOME" in my CDPATH. So, when I type 'cd folder', then folder can
> either be in the current dir or in $HOME and 'cd' will switch to
> whatever is first in CDPATH. A bit dangerous, but I came to like it.
>
> I still don't see why this affects dir parsing of coccinelle...
By default, Coccinelle chooses relevant files using git grep. This
requires a cd to the specified directory. With the CDPATH variable set,
cd to a relative path prints the full path of the destination to standard
output. That is collected as part of the standard output of the command
(I asked for drivers/usb):
cd drivers/usb; git grep -l -w \( -e kmalloc \) -- '*.c'
I can redirect the output of cd to /dev/null.
julia
next prev parent reply other threads:[~2024-04-16 16:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 21:05 [cocci] new version 1.2 Julia Lawall
2024-03-28 21:33 ` Gustavo A. R. Silva
2024-03-29 7:14 ` [cocci] Version 1.2 released Markus Elfring
2024-03-29 10:33 ` Julia Lawall
2024-04-11 20:58 ` [cocci] new version 1.2 Wolfram Sang
2024-04-11 21:05 ` Julia Lawall
2024-04-12 6:29 ` Wolfram Sang
2024-04-12 6:33 ` Julia Lawall
2024-04-12 6:50 ` Wolfram Sang
2024-04-12 6:59 ` Julia Lawall
2024-04-12 8:23 ` Wolfram Sang
2024-04-12 10:42 ` Wolfram Sang
2024-04-16 12:15 ` Julia Lawall
2024-04-16 12:23 ` Wolfram Sang
2024-04-16 16:07 ` Julia Lawall [this message]
2024-04-16 19:29 ` Wolfram Sang
2024-05-03 14:16 ` Denis Efremov
2024-05-03 15:32 ` Julia Lawall
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=762b29b1-c2ba-e9e6-1054-5d4bf54b6843@inria.fr \
--to=julia.lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@kernel.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.
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).