From: "Nagy Balázs" <js@iksz.hu>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: Frank <streamlake@tiscali.it>, git@vger.kernel.org
Subject: Re: Cygwin: problem with renaming and case
Date: Sat, 22 Mar 2008 20:58:45 +0100 [thread overview]
Message-ID: <47E564F5.6010005@iksz.hu> (raw)
In-Reply-To: <37fcd2780803211157n15cec620gb5ab1d3e57ccd37b@mail.gmail.com>
Dmitry Potapov wrote:
> 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.
>
qmail-1.03 is one of the rare species which has two files which differ
only in their case, namely INSTALL and install. The first one contains
the documentation, the latter one is compiled from source. Apart from
that I don't know any other affected projects.
On the other hand, most of the software developers are morons,
especially in a corporate environment. The problem is you cannot refuse
their work all the way, and they like to create evil twins (file names
which were removed and added again), and case collisions. I could even
see a lot of symlinks in a clearcase vob which poined to
`..\..\..\../a/b/c'. Developer stupidity is unlimited.
Regards,
--
-jul-
next prev parent reply other threads:[~2008-03-22 19:59 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
2008-03-21 19:54 ` Brian Dessent
2008-03-22 19:58 ` Nagy Balázs [this message]
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=47E564F5.6010005@iksz.hu \
--to=js@iksz.hu \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=streamlake@tiscali.it \
/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