From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jan Wielemaker <wielemak@science.uva.nl>
Cc: git@vger.kernel.org
Subject: Re: git filter-branch --subdirectory-filter error
Date: Mon, 22 Oct 2007 14:44:25 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710221440540.25221@racer.site> (raw)
In-Reply-To: <200710221337.50730.wielemak@science.uva.nl>
Hi,
On Mon, 22 Oct 2007, Jan Wielemaker wrote:
> On Monday 22 October 2007 13:20, Johannes Schindelin wrote:
>
> > The subdirectory filter does not look kindly upon a history where some
> > commits lack the subdirectory in question. However, this should work:
> >
> > git filter-branch --subdirectory--filter RDF 95807fe01..HEAD
>
> Thanks, but ... hmmm.
>
> $ git filter-branch --subdirectory-filter RDF
> 95807fe01c39d3092e3ac3a98061711323154d77..HEAD
> Rewrite 0a43c802dd60f53d48136a32526a4b2a5f0d43e5 (1/11)fatal: Not a valid
> object name 0a43c802dd60f53d48136a32526a4b2a5f0d43e5:RDF
> Could not initialize the index
I suspect again that this commit does not contain the RDF/ subdirectory.
> This started as a big project with a lot of history in CVS, including
> moved (read deleted and re-created) files. This was moved to SVN and
> from there immediately to GIT. In GIT lots of things have been renamed.
> The RDF directory was created quite recent in the project and things
> from various subdirectories were moved there.
>
> Is there something that might be worth a try or should we go the simple
> way: keeping the old combined repo for later reference and create two
> new ones from fresh files?
It sure sounds pretty tricky. (IOW I'm probably unable to help more...)
Ciao,
Dscho
prev parent reply other threads:[~2007-10-22 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 10:27 git filter-branch --subdirectory-filter error Jan Wielemaker
2007-10-22 11:20 ` Johannes Schindelin
2007-10-22 11:37 ` Jan Wielemaker
2007-10-22 13:44 ` 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=Pine.LNX.4.64.0710221440540.25221@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=wielemak@science.uva.nl \
/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).