From: Eric Frederich <eric.frederich@gmail.com>
To: git@vger.kernel.org
Subject: remove all traces of some files
Date: Wed, 27 Apr 2011 15:58:39 -0400 [thread overview]
Message-ID: <BANLkTim_PriowuBH71M2DxxkJ=Y5oAA2uA@mail.gmail.com> (raw)
I have been adding build files (.dll and .so files) to my git
repository periodically when I have been doing builds of my project.
I know I shouldn't be doing this and want to set up some other kind of
separate archive or something for built files.
Although there are other devs on the project, I am the only one using
Git. Everyone else uses AccuRev.
Personally, I maintain my own Git repo (with an AccuRev git branch).
I would like to remove all traces of those .dll and .so files if I
could in my git repository.
I realize this would mess with hashes and would ultimately result in a
completely new tree.
I am fine with that since, as I said, I am the only user of this Git repo.
So, can this be done? Can I rebuild the tree preserving commit
messages, timestamps, etc but ignoring certain files?
Thanks,
~Eric
next reply other threads:[~2011-04-27 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 19:58 Eric Frederich [this message]
2011-04-27 20:37 ` remove all traces of some files Johannes Sixt
2011-04-27 20:40 ` Phil Hord
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='BANLkTim_PriowuBH71M2DxxkJ=Y5oAA2uA@mail.gmail.com' \
--to=eric.frederich@gmail.com \
--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).