From: "Klas Lindberg" <klas.lindberg@gmail.com>
To: "Johannes Sixt" <j.sixt@viscovery.net>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
"Michael J Gruber" <git@drmicha.warpmail.net>,
"Steven Grimm" <koreth@midwinter.com>,
"Git Users List" <git@vger.kernel.org>
Subject: Re: How to remove a commit object?
Date: Fri, 3 Oct 2008 13:42:53 +0200 [thread overview]
Message-ID: <33f4f4d70810030442l5042fdbfw18f97336c5a331cc@mail.gmail.com> (raw)
In-Reply-To: <48E4E27E.7030308@viscovery.net>
On Thu, Oct 2, 2008 at 5:02 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
>> with filter-branch, I would appreciate some guidance for using it. It
>> basically seemed to do exactly what I wanted (recreate the repo, minus
>> some explicit stuff, with history intact otherwise), except the result
>> looked crazy.
>
> And your definition of 'crazy' is...?
Right... :-)
Crazy == Obviously incorrect behaviour that I didn't analyze. Out of
167 commits on subdirectory B, only 14 survived the filtering.
I tried "git filter-branch --tree-filter 'rm -rf <list of everything
except B>' HEAD" instead, but I can't use that. The change history for
all the non-B paths are still in the repo afterwards, and thus you can
easily recreate any file outside subdirectory B.
Is there some way to do what I need with git-filter-branch today, or
must I wait until 1.6.1 is released?
BR / Klas
> I assume that you used --subdirectory-filter. This has issues that will be
> fixed in 1.6.1. You need a current 'master' git (at least b805ef08).
>
> -- Hannes
>
next prev parent reply other threads:[~2008-10-03 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 23:41 How to remove a commit object? Steven Grimm
2008-09-19 9:16 ` Michael J Gruber
2008-10-02 13:36 ` Klas Lindberg
2008-10-02 14:00 ` Michael J Gruber
2008-10-02 14:02 ` Jakub Narebski
2008-10-02 14:26 ` Klas Lindberg
2008-10-02 14:30 ` Michael J Gruber
2008-10-02 14:52 ` Klas Lindberg
2008-10-02 15:02 ` Johannes Sixt
2008-10-03 11:42 ` Klas Lindberg [this message]
2008-10-03 12:03 ` Johannes Sixt
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=33f4f4d70810030442l5042fdbfw18f97336c5a331cc@mail.gmail.com \
--to=klas.lindberg@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=jnareb@gmail.com \
--cc=koreth@midwinter.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).