From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #08; Wed, 27)
Date: Thu, 28 Aug 2008 09:17:08 +0200 [thread overview]
Message-ID: <48B650F4.3090404@viscovery.net> (raw)
In-Reply-To: <7v3akpkfwf.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
> * tr/filter-branch (Tue Aug 12 10:45:59 2008 +0200) 7 commits
> + filter-branch: use --simplify-merges
> + filter-branch: fix ref rewriting with --subdirectory-filter
> + filter-branch: Extend test to show rewriting bug
>
> Fixes a longstanding filter branch bug. Success stories?
> Later parts depends on the earlier part of "--simplify-merges"
I have a repo to split that *requires* this. But I failed to complete the
task because there's a problem with rev-list --parents --full-history
--reverse that lists a commit without parent where there should be a
parent (it lists it correctly if --reverse is dropped). A test repository
is available in this messaged:
http://thread.gmane.org/gmane.comp.version-control.git/93171
-- Hannes
next prev parent reply other threads:[~2008-08-28 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 2:54 What's cooking in git.git (Aug 2008, #08; Wed, 27) Junio C Hamano
2008-08-28 7:17 ` Johannes Sixt [this message]
2008-08-28 10:56 ` Stephen R. van den Berg
2008-08-28 11:07 ` 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=48B650F4.3090404@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).