From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: getting git to ignore modifications to specific files
Date: Wed, 01 Sep 2010 13:06:33 -0600 [thread overview]
Message-ID: <4C7EA439.2000901@workspacewhiz.com> (raw)
In-Reply-To: <4C7EA1FF.8030307@gmail.com>
----- Original Message -----
From: Chris Packham
Date: 9/1/2010 12:57 PM
> I did a bit of googling and found
> git update-index --assume-unchanged
>
> Which works locally to stop git status from complaining. Is there anyway
> for me to make a change to our clone (a .gitattribues entry?) so that
> everyone can get this by default?
I don't think so (but I hope I'm wrong!).
Good idea, though. +1 from me for being necessary.
Josh
next prev parent reply other threads:[~2010-09-01 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 18:57 getting git to ignore modifications to specific files Chris Packham
2010-09-01 19:06 ` Joshua Jensen [this message]
2010-09-01 19:12 ` Bruce Korb
2010-09-01 20:45 ` Chris Packham
2010-09-01 19:24 ` Joshua Juran
2010-09-02 4:09 ` Jonathan Nieder
2010-09-02 9:25 ` Jan Krüger
2010-09-02 10:20 ` Michael J Gruber
2010-09-02 19:40 ` Chris Packham
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=4C7EA439.2000901@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=git@vger.kernel.org \
--cc=judge.packham@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.