From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Removing things from a repo that shouldn't be there
Date: Sun, 10 Feb 2008 17:38:20 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0802101738120.11591@racer.site> (raw)
In-Reply-To: <9e4733910802100915t56d0f63fh90c303b35f6af921@mail.gmail.com>
Hi,
On Sun, 10 Feb 2008, Jon Smirl wrote:
> In the lazy clone thread there is mention of a large, generated file
> being checked into the tree. Let's say we have a tree like this and it
> is ok to delete the generated file since it didn't really need to be
> checked in. Is there a procedure to chase down all the revisions, delete
> them, and then regenerate the commits to reflect the deletion? I don't
> need this tool, I'm just wondering if there is a reasonable solution to
> the problem.
filter-branch.
Ciao,
Dscho
prev parent reply other threads:[~2008-02-10 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 17:15 Removing things from a repo that shouldn't be there Jon Smirl
2008-02-10 17:38 ` Johannes Schindelin [this message]
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=alpine.LSU.1.00.0802101738120.11591@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jonsmirl@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