X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=iGBL4r+JN7+85kSfq0V79bkk3nMyWWvORy0IfNLFhXA=;
	b=eSddl0WSkgycT1TkjCJhqd2jiB9g2BKgezXBSIYiTpG4S57L314dLrGRl56brYu8nD
	GyMC5lHDSNTRDLDtxBv07DnVWc54Mxxbn7fADiHlUi3XqgizIXzDVPD8UhRgfoGSmCqv
	IXHHsN4MOaDYfxuWZl3v2+wmwMoz8fL5PFLPbBYrpgp4KCVcWDptBw6Aa/dok4Dm3bUT
	ur8Q+7h8GK8hfcEcvUp676smsFN8HWGs1ccDo7DSSv1pUpr7SKLzyTvIKUyk9fnDLM/M
	DnZEccgAb2l7/ba+9IBsFeUy8eedGMShwEDdZQAmf10DZ3U8e2xBflgh4ZOaZoDnyCyc
	NdIg==
MIME-Version:	1.0
X-Received:	by 10.50.67.100 with SMTP id m4mr13052688igt.32.1427103697238;
	Mon, 23 Mar 2015 02:41:37 -0700 (PDT)
In-Reply-To:	<550F2526.5040002@iki.fi>
References:	<CAA2C=vCQW+5FhuCvCU7F9OfCFg53JXuO6W7Q5bhXSSWhh3SbqQ AT mail DOT gmail DOT com>
	<550F2526 DOT 5040002 AT iki DOT fi>
Date:	Mon, 23 Mar 2015 11:41:37 +0200
Message-ID:	<CAA2C=vCEWVQDYWbeRL0u9srC2bbW5oxWnjJPE3B5o9xhNNw3-g@mail.gmail.com>
Subject:	Re: djgpp cvsroot
From:	Ozkan Sezer <sezeroz AT gmail DOT com>
To:	djgpp AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t2NA532F019515
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 3/22/15, Andris Pavenis <andris DOT pavenis AT iki DOT fi> wrote:
> On 03/22/2015 11:52 AM, Ozkan Sezer wrote:
>> Hi:  Is there a way to get the cvsroot for djgpp (rsync or something)
>> so one can fork it with history at github, etc?  Thanks.
>>
>> --
>> O.S.
>>
>
> I have not tried importing CVS to GIT, but Google returns some recipes
> like:
> https://stackoverflow.com/questions/584522/how-to-export-revision-history-from-mercurial-or-git-to-cvs/586225#586225
>

Thanks.  I tried that git-cvsimport thing (using tool provided by fedora20)
but failed, won't try it further

> My own experience is with using GIT with remote SVN repos. Generally works
> OK. Only initial
> checkout reads all revisions and taḱes really long time. I guess it could be
> something similar with
> CVS and GIT. Local copy of DJGPP CVS repo could be preferred if so.

If I had the local copy of the cvs repo, I can do the rest just fine, i.e.
fork a new cvs or svn or git repo, but it's not available.  Oh well, I won't
pursue this.

--
O.S.

- Raw text -