git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Palmer <wmpalmer@gmail.com>
To: Thomas Berg <merlin66b@gmail.com>
Cc: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>, git@vger.kernel.org
Subject: Re: [BUG?] Fresh clone of jquery.git shows modifications?
Date: Wed, 18 Aug 2010 17:37:36 +0100	[thread overview]
Message-ID: <1282149456.24584.114.camel@wpalmer.simply-domain> (raw)
In-Reply-To: <AANLkTik8RGR4OTeZYsttyBtiywGU7Wtz3gQsTjoqAQPD@mail.gmail.com>

On Wed, 2010-08-18 at 17:50 +0200, Thomas Berg wrote:
> Hi,
> [snip]
> > Just to re-state: This is not "my repository". That is, I don't consider
> > it to be. So I would prefer only solutions which involve editing
> > something unversioned, such as .git/config, rather than making random
> > patches which feel very much like work-arounds to a git problem.
> 
> Such a solution exists, you can create a file .git/info/attributes,
> which will override the faulty .gitattributes file in the repository
> [1]. Then you could make git treat all files as binary files, making
> no conversions. Using this unversioned file also enables you to jump
> back in history, rebase etc. without problems.
> 

.git/info/attributes
* -crlf

seems to be what I was looking for! Thank you.

Though I very much think the way git currently acts in this situation is
quite inexcusably broken.

> Hope this helps,
> Thomas
> 
> [1] http://www.kernel.org/pub/software/scm/git/docs/gitattributes.html

  reply	other threads:[~2010-08-18 16:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 12:40 [BUG?] Fresh clone of jquery.git shows modifications? Will Palmer
2010-08-18 13:18 ` Eyvind Bernhardsen
2010-08-18 14:14   ` Will Palmer
2010-08-18 15:50     ` Thomas Berg
2010-08-18 16:37       ` Will Palmer [this message]
2010-08-18 18:09         ` Eyvind Bernhardsen
2010-08-18 19:19       ` Eyvind Bernhardsen
2010-08-18 19:49         ` Thomas Berg
2010-08-18 18:55     ` Eyvind Bernhardsen

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=1282149456.24584.114.camel@wpalmer.simply-domain \
    --to=wmpalmer@gmail.com \
    --cc=eyvind.bernhardsen@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=merlin66b@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).