From: Dmitry Potapov <dpotapov@gmail.com>
To: Johannes Sixt <johannes.sixt@telecom.at>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Alex Riesen <raa.lkml@gmail.com>, Marcus Griep <marcus@griep.us>
Subject: Re: [PATCH 4/4] cygwin: Use native Win32 API for stat
Date: Sun, 28 Sep 2008 01:54:06 +0400 [thread overview]
Message-ID: <20080927215406.GG21650@dpotapov.dyndns.org> (raw)
In-Reply-To: <200809272035.03833.johannes.sixt@telecom.at>
On Sat, Sep 27, 2008 at 08:35:03PM +0200, Johannes Sixt wrote:
>
> > +core.cygwinNativeStat::
>
> This name is *really* odd, for two reasons:
>
> - If I read "native" in connection with Windows, I would understand Windows's
> implementation as "native". Cygwin is not native - it's a bolted-on feature.
>
> - This name talks about the implementation, not about its effect.
>
> Perhaps a better name would be core.ignoreCygwinFSFeatures, and the
> description would only mention that setting this to true (the default) makes
> many operations much faster, but makes it impossible to use File System
> Features A and B and C in the repository. "If you need one of these features,
> set this to false."
>
> (And after writing above paragraphs I notice, that you actually really meant
> Windows's "native" stat; see how confusing the name is?)
It was Shawn's suggestion. I don't care much about the name as long as
it is explained in the documentation... Therefore, I accepted what Shawn
said without giving it any thought. Now, when you bring this name to my
attention, I believe core.useCygwinStat (in the opposite to the current
core.cygwinNativeStat) would be a better name. Your name is okay too,
but a bit too long for my taste and not specific enough (I suppose
Cygwin does many FS related tricks). Anyway, I don't have a strong
opinion here, so just whatever most people like is fine with me :)
>
> > +static inline void filetime_to_timespec(const FILETIME *ft, struct
> > timespec *ts) +{
> > + long long winTime = ((long long)ft->dwHighDateTime << 32) +
> > ft->dwLowDateTime; + winTime -= 116444736000000000LL; /* Windows to Unix
> > Epoch conversion */ + ts->tv_sec = (time_t)(winTime/10000000); /*
> > 100-nanosecond interval to seconds */ + ts->tv_nsec = (long)(winTime -
> > ts->tv_sec*10000000LL) * 100; /* nanoseconds */ +}
>
> Shorter lines in this function would be appreciated (and not just because my
> MUA can't deal with them ;).
I am sorry, I did not notice that the line got longer than 80 columns.
I will resent the patch once the issue with the name of the option is
resolved.
Dmitry
next prev parent reply other threads:[~2008-09-27 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 8:43 [PATCH 4/4] cygwin: Use native Win32 API for stat Dmitry Potapov
[not found] ` <347507080809270851y79764dbcgba1ef5a1d58bdd3e@mail.gmail.com>
2008-09-27 16:33 ` Dmitry Potapov
2008-09-27 18:35 ` Johannes Sixt
2008-09-27 21:54 ` Dmitry Potapov [this message]
2008-09-28 9:24 ` Johannes Sixt
2008-09-29 15:34 ` Shawn O. Pearce
2008-09-29 18:26 ` Dmitry Potapov
2008-09-30 13:53 ` [PATCH 4/4 v2] " Dmitry Potapov
2008-09-30 14:57 ` Marcus Griep
2008-09-30 20:26 ` Shawn O. Pearce
2008-09-28 9:50 ` [PATCH 4/4] " Alex Riesen
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=20080927215406.GG21650@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.sixt@telecom.at \
--cc=marcus@griep.us \
--cc=raa.lkml@gmail.com \
--cc=spearce@spearce.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).