From: Jonathan Nieder <jrnieder@gmail.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, 1 Sep 2010 23:09:09 -0500 [thread overview]
Message-ID: <20100902040909.GD29713@burratino> (raw)
In-Reply-To: <4C7EA1FF.8030307@gmail.com>
Chris Packham wrote:
> There are a couple of repositories that are local clones of 3rd party
> repositories which have included the pesky auto-generated files so whle
> I can remove the offending files from repositories we control I need
> another solution for the 3rd part ones.
FWIW one half-solution that has worked well for me is to make a local
clone without the autogenerated files and complain to upstream so the
local clone becomes superfluous after a while.
Naturally another solutions might work better, though.
next prev parent reply other threads:[~2010-09-02 4:11 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
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 [this message]
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=20100902040909.GD29713@burratino \
--to=jrnieder@gmail.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 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).