Re: cvs2git reports a "sprout" from a nonexistent commit?

Robert Haas <robertmhaas@gmail.com> writes:
> On Sun, Sep 12, 2010 at 12:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> There are a couple of weird-looking commits way back near the beginning
>> of the converted Postgres history:
>> 
>> commit 91f2ac21a1e085dfe81aae110cee2246a803f600 refs/tags/Release_2_0_0
>> Author: PostgreSQL Daemon <webmaster@postgresql.org>
>> Date: � Sat Aug 17 06:41:11 1996 +0000
>> 
>> � �This commit was manufactured by cvs2svn to create tag 'Release_2_0_0'.
>> 
>> � �Sprout from Release_1_0_3 1996-08-02 01:24:01 UTC PostgreSQL Daemon <webmaster@postgresql.org> 'This commit was
manufacturedby cvs2svn to create branch 'Release_1_0_3'.'
 
>> � �Cherrypick from master 1996-08-17 06:41:10 UTC Marc G. Fournier <scrappy@hub.org> 'changed missed err() change to
err_out()':

>> What is weird about them is that the referenced "sprout" commit doesn't
>> exist. �Is this expected behavior?

> What commit do you think doesn't exist?

There is no commit with a log message like 'This commit was manufactured
by cvs2svn to create branch 'Release_1_0_3'.'

There is a another strange thing about these two commits: AFAICS they
shouldn't exist at all.  Their content ought to be exactly the same as
the immediately preceding mainline commits, so why didn't cvs2git just
apply the branch tags to those mainline commits, instead of sprouting
from a significantly earlier point on the mainline and then having to
duplicate all the diffs from that time to this?
        regards, tom lane