> I'm guessing the cvs2git version changed in the upgrade and the new version
> generates different commit hashes from the old one. You can verify this by
> comparing how a known commit shows up on the GitHub UI vs. a git log of a
> recent cvs2git conversion: if the "commit XXX" strings differ
>> I know many here are using CVS, and many are also using git, so I wonder
>> if anybody can help me. On BSD.lv, I push my CVS repositories (kcgi,
>> sblg, etc.) to GitHub from time to time using a cvs2git script. It goes
>> as follows, shortened and pseudonymised:
>>
>> REPO=$1 # e.g., kcgi
>
I'm guessing the cvs2git version changed in the upgrade and the new version
generates different commit hashes from the old one. You can verify this by
comparing how a known commit shows up on the GitHub UI vs. a git log of a
recent cvs2git conversion: if the "commit XXX" strings differ, that's
On Fri, Jan 19, 2018 at 01:43:08PM +0700, Kristaps Dzonsons wrote:
> I know many here are using CVS, and many are also using git, so I wonder
> if anybody can help me. On BSD.lv, I push my CVS repositories (kcgi,
> sblg, etc.) to GitHub from time to time using a cvs2git script. It goes
> as follo
I know many here are using CVS, and many are also using git, so I wonder
if anybody can help me. On BSD.lv, I push my CVS repositories (kcgi,
sblg, etc.) to GitHub from time to time using a cvs2git script. It goes
as follows, shortened and pseudonymised:
REPO=$1 # e.g., kcgi
cd /tmp/cvs2git
5 matches
Mail list logo
