From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] Disable filemode rebase tests in t3400-rebase.sh if no filesystem mode support
Date: Wed, 11 Feb 2009 12:05:08 +0100 [thread overview]
Message-ID: <81b0412b0902110305o5ca60708gc07cbc9ae1d89d1f@mail.gmail.com> (raw)
In-Reply-To: <7v7i3xgu9v.fsf@gitster.siamese.dyndns.org>
2009/2/11 Junio C Hamano <gitster@pobox.com>:
> Alex Riesen <raa.lkml@gmail.com> writes:
>
>> Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
>> ---
>>
>> I'm honestly sorry for my contributions. They seem to be exclusively
>> in the "make Git work in Windows" area. Depressing.
>>
>> t/t3400-rebase.sh | 5 +++++
>> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> I wonder if you should be fixing the tests with "update-index --chmod"
> instead...
>
Well, mostly these should work independent of the filesystem (except
for the cases when the index is checked out later). They seem to, and
they look like they should, too. See t4014-format-patch, for one.
But you're right. I should have reviewed them earlier. Anyway, there is
not many tests which have "--chmod" in them:
t4006-diff-mode.sh, t4014-format-patch.sh, t6031-merge-recursive.sh,
and t9500-gitweb-standalone-no-errors.sh.
The t4006 does not bother to look at working tree (good),
t4014 is good (looks like its ignoring modes altogether),
t6031 uses --chmod to augment the chmod useless on FAT-like fs
(seem to be an earlier fix for the same problem).
What's more interesting is the use of chmod for index mode change purpose,
which should be reviewed regularly (and I do that only when it breaks.
Lazy boom, I am...)
next prev parent reply other threads:[~2009-02-11 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 9:51 [PATCH] Disable filemode rebase tests in t3400-rebase.sh if no filesystem mode support Alex Riesen
2009-02-11 10:09 ` Junio C Hamano
2009-02-11 11:05 ` Alex Riesen [this message]
2009-02-11 10:09 ` Johannes Sixt
2009-02-11 10:53 ` Alex Riesen
2009-02-11 11:30 ` Johannes Sixt
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=81b0412b0902110305o5ca60708gc07cbc9ae1d89d1f@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).