From: Aleksandr Dubinsky <adubinsky@almson.net>
To: git@vger.kernel.org
Subject: Suggested behavior when pulling .gitattributes
Date: Sun, 2 Sep 2012 02:21:51 +0300 [thread overview]
Message-ID: <CAEbpm93Pr8sU9mBx8V5VMmi5aXos-KBQpmEN7NPrdR07rYV5EQ@mail.gmail.com> (raw)
Hi,
I ran into a problem with line endings that .gitattributes is supposed
to fix. However, I ran into a headache with this not giving the
desired result. This headache could have easily been avoided if:
When pulling .gitattributes, git should parse the file and anything
new in it should be acted upon. Specifically, if a file already exists
with modified endings and .gitattributes now says it should be treated
as binary, then please automatically re-checkout the file with the
correct, un-modified line endings.
Possibly this suggestion also applies to pushing/committing but that
wasn't the problem I ran into just now.
reply other threads:[~2012-09-01 23:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAEbpm93Pr8sU9mBx8V5VMmi5aXos-KBQpmEN7NPrdR07rYV5EQ@mail.gmail.com \
--to=adubinsky@almson.net \
--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;
as well as URLs for NNTP newsgroup(s).