From: Jon Seymour <jon.seymour@gmail•com>
To: lode leroy <lode_leroy@hotmail•com>
Cc: git@vger•kernel.org
Subject: [RFC] Is there a need for binary bit in cache/tree entries to properly support Cygwin builds of GIT?
Date: Fri, 22 Apr 2005 18:53:17 +1000 [thread overview]
Message-ID: <2cfc403205042201534bef0276@mail.gmail.com> (raw)
In-Reply-To: <BAY22-F35C035C6AE6B9A45CDEF61FF2D0@phx.gbl>
On 4/22/05, lode leroy <lode_leroy@hotmail•com> wrote:
> I wonder if anyone is interested in using git on windows / cygwin.
> It almost compiles out of the box... just this one little thinggy
> that's glibc-specific (struct dirent . d_type)
>
I wonder if a cygwin compile of GIT should be forced to strip CR's
from text files prior to checksum calculations and blob storage.
Otherwise, spurious differences may be introduced into text files that
are somehow munged while checked out in a Windows environment.
There is an argument that this should be done external to the GIT
core, but then every external non-unix tool that interacts with GIT
has to have heuristics to distinguish text from binary and they all
have to have the same heuristics.
So, perhaps there is an argument for using one of the unused "mode"
bits to encode a binary flag and add an option to update-cache that
allows the bit to be flipped if a blob is known to be binary. A cygwin
GIT binary could then be forced to strip CR's from blobs marked as
text, but a unix binary need not change its behaviour.
Regards,
jon.
prev parent reply other threads:[~2005-04-22 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 8:09 (nearly trivial) patch to compile git on cygwin lode leroy
2005-04-22 8:53 ` Jon Seymour [this message]
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=2cfc403205042201534bef0276@mail.gmail.com \
--to=jon.seymour@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jon@zeta$(echo .)org.au \
--cc=lode_leroy@hotmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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