From: streamlake@tiscali.it
To: git@vger.kernel.org
Subject: Re: Cygwin: problem with renaming and case
Date: Fri, 21 Mar 2008 20:37:48 +0100 [thread overview]
Message-ID: <47E40E8C.9040805@tiscali.it> (raw)
In-Reply-To: <37fcd2780803211157n15cec620gb5ab1d3e57ccd37b@mail.gmail.com>
Dmitry Potapov ha scritto:
>
>
> I wonder do you really need to have two files on different branches whose
> name only differ by case, especially when you work on case insensitive
> filesystem? I suspect the answer is no. In this case, you can choose one
> policy for file naming and stick to it. For instance, that all names should
> be in low case except Makefile, or something like that. This policy can be
> enforced using pre-commit hook.
>
> Dmitry
>
>
You're right, in fact it usually happens as the result of a mistake in
naming a file between two branches or deleting a file and creating
another one months later with the same name, not really a question of
policies... :-)
@Linus
As always, I'm absolutely not a windz fan (and this is demonstrated by
the fact that I've been using cygwin for long time instead of the crappy
win command prompt, and use linux every day for a few non-strictly-windz
projects), but I 'must' use it if I want to work, there's no choice
where I come from, and I can't change the market by myself, even if I
strongly support linux as a substitute...
So, given the fact that git is almost 'officially' supported at least
under cygwin, I think it would be a good idea, if technically possible,
to have a look at this kind of features. Not to mention the fact that
having a broader audience for a project like git can be positive...
Thanks for your help,
Frank
next prev parent reply other threads:[~2008-03-21 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 16:07 Cygwin: problem with renaming and case Frank
2008-03-21 17:46 ` Linus Torvalds
2008-03-21 17:57 ` Avery Pennarun
2008-03-21 18:09 ` Linus Torvalds
2008-03-22 0:32 ` Junio C Hamano
2008-03-22 13:45 ` Steffen Prohaska
2008-03-21 18:57 ` Dmitry Potapov
2008-03-21 19:37 ` streamlake [this message]
2008-03-21 19:54 ` Brian Dessent
2008-03-22 19:58 ` Nagy Balázs
2008-03-22 20:18 ` Linus Torvalds
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=47E40E8C.9040805@tiscali.it \
--to=streamlake@tiscali.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox