Re: ELKS Git repository up on SourceForge + patches applied

I personally think the CVS history should be kept. This actually ends
up being pretty trivial with git cvsimport. I've already done this in
the past and it works well, it even got all the various tags (going
back to elks-0_0_73-pre2-start 1998-09-12 11:10:05 (CDT)) The resulting
repo ends up being about 2Mb. So you can either use cvsimport
yourself, or you can grab my copy here:
git://losinggeneration.dyndns.org/elks_upstream.git

I also have elkscmd.git, elksnet.git, & elksutils.git from the same
base URL. 


On Sun, 05 Feb 2012 14:22:15 -0500
Jody <[email protected]> wrote:

> I just pushed the code to Git. I don't know much about CVS and I have 
> always personally hated it since I got on SourceForge 11 years ago. I 
> just wanted to get the code in an easily reachable place as quickly
> as I could, so that's what I've done. Do we need the CVS history,
> moving forward?
> 
> On 2/5/2012 2:18 PM, Kirn Gill wrote:
> >
> > That's one better than I had planned. I was just going to push the 
> > changes to CVS and call it a day. Say, did you import all the CVS 
> > history into git or just a checkout of the latest sources + the
> > patches?
> >
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086"
> in the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html