From: Dmitry Potapov <dpotapov@gmail.com>
To: Steffen Prohaska <prohaska@zib.de>
Cc: gitster@pobox.com, torvalds@linux-foundation.org, git@vger.kernel.org
Subject: Re: [PATCH] Don't display crlf warning twice
Date: Mon, 14 Jan 2008 09:40:36 +0300 [thread overview]
Message-ID: <20080114064036.GX2963@dpotapov.dyndns.org> (raw)
In-Reply-To: <B4297A2E-9F8F-4167-AB48-10AC1FB4E1D5@zib.de>
On Mon, Jan 14, 2008 at 07:17:26AM +0100, Steffen Prohaska wrote:
>
> Your traces reveal that it is a racy condition that can trigger
> the double warnings.
It is not a racy condition. It is just another branch in the
code, which happens when an existing file is modified. Your
tests always added a new file, so they could not reproduce
the problem.
>
> Do you have a test case that reliably triggers the second call to
> convert_to_git()?
===========================================
git config core.autocrlf input
echo Hello > foo
git add foo
git commit -m 'add foo'
echo Hello >> foo
unix2dos foo
# This should trigger double crlf warning
git add foo
===========================================
Dmitry
next prev parent reply other threads:[~2008-01-14 6:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 16:30 [PATCH v3] safecrlf: Add mechanism to warn about irreversible crlf conversions Steffen Prohaska
2008-01-13 22:02 ` Dmitry Potapov
2008-01-13 22:13 ` Dmitry Potapov
2008-01-13 23:46 ` [PATCH] Don't display crlf warning twice Dmitry Potapov
2008-01-14 6:17 ` Steffen Prohaska
2008-01-14 6:40 ` Dmitry Potapov [this message]
2008-01-14 6:53 ` Steffen Prohaska
2008-01-14 23:20 ` [PATCH] safecrlf: Add flag to convert_to_git() to disable safecrlf check Steffen Prohaska
2008-01-14 23:58 ` Junio C Hamano
2008-01-15 20:52 ` Steffen Prohaska
2008-01-15 21:41 ` Steffen Prohaska
2008-01-15 23:23 ` Junio C Hamano
2008-01-15 10:26 ` Dmitry Potapov
2008-01-15 20:39 ` Steffen Prohaska
2008-01-15 23:03 ` Dmitry Potapov
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=20080114064036.GX2963@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=prohaska@zib.de \
--cc=torvalds@linux-foundation.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).