From: Mike Hommey <mh@glandium.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Pascal Obry <pascal@obry.net>, git list <git@vger.kernel.org>
Subject: Re: Problem with git filter-branch
Date: Sat, 25 Oct 2008 22:40:12 +0200 [thread overview]
Message-ID: <20081025204012.GA26295@glandium.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0810252235040.22125@pacific.mpi-cbg.de.mpi-cbg.de>
On Sat, Oct 25, 2008 at 10:36:26PM +0200, Johannes Schindelin wrote:
> Hi,
>
> On Sat, 25 Oct 2008, Pascal Obry wrote:
>
> > Anyway, I used to run the following command:
> >
> > $ git filter-branch --tag-name-filter cat --parent-filter "sed -e
> > 's/^$/-p c96d4da294667de1800687d25340551683153002/'" svn-release_2_6
> >
> > without problem, I now get this:
> >
> > Namespace refs/original/ not empty
> > rm: cannot remove directory
> > `/home/obry/dev/repositories/git/proj/.git-rewrite': Directory not empty
>
> It is a (maybe ill-conceived) feature. When branches are rewritten, their
> original versions are stored in the refs/original/ namespace. You can
> force overwriting with "-f".
>
> I wonder if people would like to have this feature removed; reflogs should
> be enough.
I have never have had use for the refs/original namespace, and I used
filter-branch more than a couple of times. Though I would certainly
understand that people would not be confident enough not to have a
parachute. Reflog would indeed be enough, as long as it is not
branch@{42000} that needs to be used. Haven't checked, but theorically,
it should be branch@{1} in all cases, so no problem here.
Mike
next prev parent reply other threads:[~2008-10-25 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 9:33 Problem with git filter-branch Pascal Obry
2008-10-25 20:36 ` Johannes Schindelin
2008-10-25 20:40 ` Mike Hommey [this message]
2008-10-25 20:55 ` Pascal Obry
2008-10-26 5:07 ` Jeff King
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=20081025204012.GA26295@glandium.org \
--to=mh@glandium.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pascal@obry.net \
/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).