From: Johannes Sixt <j.sixt@viscovery.net>
To: Yves Orton <yves.orton@booking.com>
Cc: git@vger.kernel.org
Subject: Re: git-fast-export bug, commits emmitted in incorrect order causing parent data to be lost from commits turning essentially linear repo into "islands"
Date: Thu, 12 Jun 2008 14:45:57 +0200 [thread overview]
Message-ID: <48511A85.9020200@viscovery.net> (raw)
In-Reply-To: <1213272962.6940.231.camel@gemini>
Yves Orton schrieb:
> BTW, for the record this was needed because we are trying to merge
> multiple git repos into a single new git repo with each original repo
> mapped into a subdirectory of the new repo, and with commit trees merged
> in more or less the correct order (by date applied more or less). IOW we
> dont want to have multiple "root commits" that are later merged.
Try --date-order instead. It might work better for your task, and it still
offers a topologically correct order.
-- Hannes
next prev parent reply other threads:[~2008-06-12 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 10:21 git-fast-export bug, commits emmitted in incorrect order causing parent data to be lost from commits turning essentially linear repo into "islands" Yves Orton
2008-06-12 11:53 ` Johannes Sixt
2008-06-12 12:04 ` Yves Orton
2008-06-12 12:16 ` Yves Orton
2008-06-12 12:45 ` Johannes Sixt [this message]
2008-06-12 12:52 ` Michael J Gruber
2008-06-12 14:02 ` Philippe Bruhat (BooK)
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=48511A85.9020200@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=yves.orton@booking.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).