From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Timothy Rice <timothy.rice@unimelb.edu.au>
Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, git@vger.kernel.org
Subject: Re: Q: Ignore ./foo, but not script/foo
Date: Thu, 19 Jul 2018 11:30:08 +0200 [thread overview]
Message-ID: <871sbzd13z.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20180719090656.GA18624@sleipnir>
On Thu, Jul 19 2018, Timothy Rice wrote:
>> How did you come up with this "./" syntax?
>
> It is a Unix thing: "./" or just "." refers to the current directory.
>
> When calling scripts or programs in the current directory from a Unix
> command line, it is required to refer to them as, say, "./foo" (not just
> "foo") -- unless "." is in your PATH.
>
> Most people do put "." in their PATH for convenience but it is considered a
> little unsafe [1].
>
> Personally, I am surprised that gitignore does not understand this
> notation. To me, OPs meaning was crystal clear: "./foo" should mean to only
> ignore the foo in the repository's root directory.
>
> [1] https://superuser.com/questions/156582/why-is-not-in-the-path-by-default
To clarify I was trying to fish for whether we'd accidentally documented
"./" somewhere since OP was making references to the docs.
next prev parent reply other threads:[~2018-07-19 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 7:38 Q: Ignore ./foo, but not script/foo Ulrich Windl
2018-07-19 8:01 ` 3Ævar Arnfjörð Bjarmason
2018-07-19 9:06 ` Timothy Rice
2018-07-19 9:22 ` Konstantin Khomoutov
2018-07-19 9:30 ` Ævar Arnfjörð Bjarmason [this message]
[not found] ` <CA+xP2SZJ0VN0Y7SChAx1a8joVMKMU2R9d0je801i=9SuLicF3w@mail.gmail.com>
2018-07-19 11:00 ` Antw: " Ulrich Windl
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=871sbzd13z.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.org \
--cc=timothy.rice@unimelb.edu.au \
/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.