From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Alexander Potashev <aspotashev@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] Use is_pseudo_dir_name everywhere
Date: Fri, 09 Jan 2009 00:33:53 -0800 [thread overview]
Message-ID: <7vy6xk280e.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <4966FB36.2030409@viscovery.net> (Johannes Sixt's message of "Fri, 09 Jan 2009 08:22:30 +0100")
Johannes Sixt <j.sixt@viscovery.net> writes:
> Johannes Sixt schrieb:
>> Alexander Potashev schrieb:
>>> - if ((ent->d_name[0] == '.') &&
>>> - (ent->d_name[1] == 0 ||
>>> - ((ent->d_name[1] == '.') && (ent->d_name[2] == 0))))
>>> + if (is_pseudo_dir_name(ent->d_name))
>>
>> Nit-pick: When I read the resulting code, then I will have to look up that
>> is_pseudo_dir_name() indeed only checks for "." and "..". But if it were
>> named is_dot_or_dotdot(), then I would have to do that.
>
> ... then I would *not* have to do that, of course.
I think the unstated motivation of this choice of the name is to keep the
door open to include lost+found and friends to the repertoire, and perhaps
to have an isolated place for customization for non-POSIX platforms and
for local conventions. It is more like is_uninteresting_dirent_name().
As long as this function is used only to detect and skip "uninteresting"
dirent, I think that is not a bad direction.
On the other hand, I am a bit worried about is_empty_dir() abused outside
its intended purpose to say "this directory does not have anything
interesting". E.g. "Oh, it's empty so we can nuke it":
if (is_empty_dir(dir))
rmdir(dir);
even though the current callers do not do something crazy like this (the
usual order we do things is rmdir() and then check for errors).
next prev parent reply other threads:[~2009-01-09 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 23:24 [PATCH 0/2] Allow cloning to an existing empty directory Alexander Potashev
2009-01-08 23:24 ` [PATCH 1/2] " Alexander Potashev
2009-01-08 23:24 ` [PATCH 2/2] Use is_pseudo_dir_name everywhere Alexander Potashev
2009-01-09 7:03 ` Johannes Sixt
2009-01-09 7:22 ` Johannes Sixt
2009-01-09 8:33 ` Junio C Hamano [this message]
2009-01-09 10:24 ` Alexander Potashev
2009-01-10 2:48 ` Junio C Hamano
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=7vy6xk280e.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=aspotashev@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).