From: David Greaves <david@dgreaves.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: update-cache ./test.c
Date: Sun, 01 May 2005 10:43:34 +0100 [thread overview]
Message-ID: <4274A4C6.3000400@dgreaves.com> (raw)
In-Reply-To: <20050501084145.GA30692@xi.wantstofly.org>
Lennert Buytenhek wrote:
>Hi,
>
>update-cache seems to ignore paths containing path components
>starting with a dot:
>
> pi% update-cache --add ./test.c
> Ignoring path ./test.c
> pi% update-cache --add test.c
> pi%
>
>This is slightly annoying as 'find -type f | xargs update-cache --add'
>doesn't work because of this. ('find * -type f | ...` does.) Instead
>of ignoring the file, can we just strip off the leading "./"
>
>
This is documented behaviour:
<file>
Files to act on.
Note that files begining with '.' are discarded. This includes
"./file" and "dir/./file". If you don't want this, then use
cleaner names.
The same applies to directories ending '/' and paths with '//'
"Where?" you ask...
Well, Linus hasn't accepted the docs for some reason - you have to
search the archives...
Sorry about that...
David
PS Changing this behaviour was discussed and dismissed for the core tools.
If the problem appears in Cogito however, then it's worth patching...
prev parent reply other threads:[~2005-05-01 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 8:41 update-cache ./test.c Lennert Buytenhek
2005-05-01 8:47 ` Thomas Glanzmann
2005-05-01 8:54 ` Lennert Buytenhek
2005-05-01 8:59 ` Lennert Buytenhek
2005-05-01 9:04 ` Thomas Glanzmann
2005-05-01 10:31 ` Junio C Hamano
2005-05-01 9:43 ` David Greaves [this message]
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=4274A4C6.3000400@dgreaves.com \
--to=david@dgreaves.com \
--cc=buytenh@wantstofly.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).