From: Vitor Antunes <vitor.hda@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git fast-import : How to change parent during import?
Date: Wed, 30 Mar 2011 18:25:54 +0100 [thread overview]
Message-ID: <20110330182554.5375787b@fenix.utopia.dhis.org> (raw)
In-Reply-To: <20110308222328.GE26471@elie>
Hi Jonathan,
On Tue, 8 Mar 2011 16:23:28 -0600
Jonathan Nieder <jrnieder@gmail.com> wrote:
> The "tag fixup" idea is that in VCSes like CVS, tags do not
> necessarily match the content on any branch. So the history looks
> somewhat like so (time flowing left to right):
>
> TAG
> /
> o --- o --- o --- o --- o --- o ...
>
> instead of the perhaps more sensible
>
> o --- o --- o --- TAG --- o --- o ...
>
> The side branch leading up to a tag does not correspond to any branch
> name; after it is in the correct state one can use the "tag" command
> to get it remembered in permanent history. The same technique might
> be useful whenever you are creating history that is not meant to stay
> permanently on any branch.
I don't think the TAG_FIXUP trick is what I need in this case. Assume the
following:
A --- B --- C --- D ... (branch1)
\
E --- F --- G ... (branch2)
Now assume that we are at commit D when we detect a commit to branch2. At this
point there is no way of knowing the origin commit in branch1. What is currently
being done is to use commit D as the parent of branch2, which is incorrect. But
if we assume that all branches are created through a "cp" like command, then we
know that B=E. So my idea is to go over A, B, C, etc and commit E "from:" each
one and see which results in a zero differences diff-tree.
Unfortunately, the current implementation I am using doesn't feel simple enough.
Because I'm using commands external to fast-import, I need to be constantly
making use of "checkpoint". And this seems to not be good enough, because I need
to sleep during 0.1s (didn't try other values) after each "checkpoint" before
being able to use diff-tree and similar commands. I am also forced to use the
"--force" command due to all the orphan commits I leave behind.
I would really prefer to have a simpler solution. Do you, or anyone else, see
another option?
Thanks in advance,
--
Vitor Antunes
next prev parent reply other threads:[~2011-03-30 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 1:21 git fast-import : How to change parent during import? Vitor Antunes
2011-03-08 2:44 ` Jonathan Nieder
2011-03-08 21:19 ` Vitor Antunes
2011-03-08 22:23 ` Jonathan Nieder
2011-03-09 14:21 ` Vitor Antunes
2011-03-30 17:25 ` Vitor Antunes [this message]
2011-08-28 15:23 ` Vitor Antunes
2011-08-28 23:39 ` Jonathan Nieder
2011-08-29 1:13 ` Sverre Rabbelier
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=20110330182554.5375787b@fenix.utopia.dhis.org \
--to=vitor.hda@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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).