On 10/9/12 12:17 PM, John Whitney wrote:
Thank you very much for your detailed explanations. I suspected that
efficiency concerns might be preventing a clean solution.
How about this idea... When git stores files, it could include a bit
of metadata that tells it whether the file is a binary
On 10/7/12 6:52 PM, Jeff King wrote:
Yes, but does that really have to be an issue? Is there any technical
or practical reason you can think of that the repository shouldn't
ignore those CRs?
It's significantly less efficient. Right now git only has to do the
conversion when updating the index
On 10/6/12 8:31 AM, Jeff King wrote:
On Thu, Oct 04, 2012 at 11:10:40AM -0500, John Whitney wrote:
Thank you for your response. I do see the dilemma, but having
no possible "unmodified" state is extremely inconvenient and,
as shown, breaks basic git operations.
But you have as
Andrew,
I forgot to say that all of the config settings
are not changed from the default.
---John
On 10/4/12 11:16 AM, John Whitney wrote:
Andrew,
Thanks for checking this on your machine.
This problem occurs on Mac, Windows, and Linux, and
with multiple versions of git. Note that in my
run the script like this: "sh git_failure.sh"
---John
On 10/4/12 10:21 AM, Andrew Wong wrote:
On 10/04/2012 12:35 AM, John Whitney wrote:
I just ran into a problem that I'm pretty sure is a bug in git. Just
read and run this (fairly trivial) shell script to replicate.
I trie
ng the file out, and
consider that form (or both forms) as "unmodified". It just
doesn't make sense to me that files are considered modified
immediately after checkout.
Any thoughts as to why this would not work?
---John
On 10/4/12 9:19 AM, Phil Hord wrote:
On Thu, Oct 4,
Hi all!
I just ran into a problem that I'm pretty sure is a bug in git. Just
read and run this (fairly trivial) shell script to replicate.
Thanks!
---John Whitney
git_failure.sh
Description: Bourne shell script
7 matches
Mail list logo
