From: Pete Harlan <pgit@pcharlan.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: David Hagood <david.hagood@gmail.com>, git@vger.kernel.org
Subject: Re: Git under Windows should warn or fail on entities differning only in case
Date: Fri, 12 Feb 2010 09:31:58 -0800 [thread overview]
Message-ID: <4B75908E.3060407@pcharlan.com> (raw)
In-Reply-To: <alpine.DEB.1.00.1002121412300.20986@pacific.mpi-cbg.de>
On 02/12/2010 05:14 AM, Johannes Schindelin wrote:
> Hi,
>
> Disclaimer: I am not uninterested in the subject you talk about, but my
> reply could come over as harsh, due to lack of time. If you are likely to
> be annoyed by direct criticism, delete this mail and do not reply. Thank
> you very much.
>
> On Fri, 12 Feb 2010, David Hagood wrote:
>
>> I would suggest that git should check for this case, and generate a big
>> warning about it when it happens. (Yes, it sucks burdening Git with
>> Windows' problems....)
>
> Git is burdened with Windows' problems already. That does not suck. What
> sucks is that you only suggest that Git should check the case, in effect
> asking the few Git for Windows contributors to do it, instead of
> just going ahead and scratching your own itch.
I didn't read David's patch as anything other than floating an idea.
Posting a wish item to the list without a patch seems useful to me:
1. Someone might be able to explain why the wished-for item is a bad
idea, or why it's unfeasible to implement.
2. Someone might have a flash of insight for how to implement the idea
in a few lines of code and post the patch, improving Git.
3. Someone might say, "Good idea, go ahead and make the change," and the
person with the itch now knows that the idea will be accepted.
It sounds like this is a (3), which is doing pretty well for an idea
about how to change Git :)
--Pete
next prev parent reply other threads:[~2010-02-12 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 12:40 Git under Windows should warn or fail on entities differning only in case David Hagood
2010-02-12 13:14 ` Johannes Schindelin
2010-02-12 17:31 ` Pete Harlan [this message]
2010-02-12 21:02 ` david.hagood
2010-02-12 18:19 ` Claus Färber
2010-02-12 20:38 ` Julian Phillips
2010-02-13 6:05 ` Daniel Barkalow
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=4B75908E.3060407@pcharlan.com \
--to=pgit@pcharlan.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=david.hagood@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.