From: Michael Hendricks <michael@ndrix.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: removing content from git history
Date: Wed, 21 Feb 2007 11:30:29 -0700 [thread overview]
Message-ID: <20070221183028.GA9088@ginosko.local> (raw)
In-Reply-To: <Pine.LNX.4.64.0702210904350.4043@woody.linux-foundation.org>
On Wed, Feb 21, 2007 at 09:14:44AM -0800, Linus Torvalds wrote:
>
> See "cg-admin-rewritehist" from cogito for an example of a tool that
> would do what you need done. In fact, it has this exact thing as the
> first example.
That's just what I was looking for. Thanks.
> So right now, rewriting history is an option that you can do. It will
> effectively create a totally new branch (which you can then make into a
> new repository) which has nothing in common with the old branch from the
> point where it was modified. So you can never really merge the two ever
> again, and you need to make sure that everybody who had the old repo
> contents will destroy it.
What's a decent way to make a branch into a new repository? My first
inclination is to "cp -a" the existing repository, checkout the branch,
delete all other branches and repack. That seems to have worked in my
quick test, but is there a better way?
--
Michael
next prev parent reply other threads:[~2007-02-21 18:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 16:45 removing content from git history Michael Hendricks
2007-02-21 16:56 ` Shawn O. Pearce
2007-02-21 17:17 ` J. Bruce Fields
2007-02-21 18:02 ` Linus Torvalds
2007-02-21 18:24 ` Linus Torvalds
2007-02-21 21:00 ` Shawn O. Pearce
2007-02-21 21:11 ` Linus Torvalds
2007-02-21 21:21 ` Shawn O. Pearce
2007-10-09 20:58 ` Bill Lear
2007-10-09 21:02 ` J. Bruce Fields
2007-10-09 22:25 ` Bill Lear
2007-10-10 14:41 ` Johannes Schindelin
2007-02-21 17:14 ` Linus Torvalds
2007-02-21 18:02 ` Nicolas Pitre
2007-02-21 18:13 ` Linus Torvalds
2007-02-21 18:39 ` Nicolas Pitre
2007-02-21 18:30 ` Michael Hendricks [this message]
2007-02-21 18:37 ` Shawn O. Pearce
2007-02-21 18:47 ` Linus Torvalds
2007-02-21 18:56 ` Linus Torvalds
2007-02-21 18:52 ` Nicolas Pitre
2007-02-21 19:01 ` Junio C Hamano
2007-02-21 19:33 ` Nicolas Pitre
2007-02-21 20:22 ` Junio C Hamano
2007-02-21 20:49 ` Nicolas Pitre
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=20070221183028.GA9088@ginosko.local \
--to=michael@ndrix.org \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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).