ELKS Git repository up on SourceForge + patches applied
This is an administrative note to let everyone know that:
1. I have set up the Git repository for ELKS on SourceForge,
2. I have applied Juan Perez-Sanchez's recent patches, and
3. I have pushed the resultant master branch to the SF Git repo.
Read-only repository access is available to anyone at:
git://elks.git.sourceforge.net/gitroot/elks/elks
Additionally, I wish to continue discussing options for making ELKS less 8086-specific, and moving to a compiler that can make ELKS more easily portable.
Thanks to everyone!
Jody Bruchon
A message that is not in the archive (sent off-list or not yet received): CAMKR1ysAyZ7sDkmOBnDCcgs1rtLKQ_jnmRWJodAJg1Kp8cYebA@mail.gmail.com
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?
Quoted 4 lines · Kirn Gill
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?
Not per se, but it does allow bored students to see "what once was", or generate visual change graphs.
Just think of, say, Wine, which managed to import all their version control history from CVS into SVN, and I think now into Git as well. You can easily go back and see what Wine looked like back in 1994, if you're ever curious.
Quoted 11 lines · Jody
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?
Quoted 4 lines · Kirn Gill
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
I know there is a way to export a complete CVS repository with history to git as I did so recently for an other project also on sourceforge (csvjdbc), I can't remember much more than it was an extension to git, but google for it and you will surely find it.
if it was me doing the transition, I would definitely keep the cvs
history: I would either construct and publish a git repository that holds the full cvs history of elks and remove the csv server. as a second choice I would keep the cvs server in its place but make it read-only.
YMMV
MF
Quoted 14 lines · 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?
Quoted 7 lines · Kirn Gill
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?
I mentioned to Jody off-list that Git has a tool for performing such an import. I've commit access as "segin" on sf.net; so I'll try to use that account to perform the conversion.
Hopefully Jody also commits the recent changes to CVS as well in case I must reset the Git repository; I'd do it myself but my development box is offline for a while. I'm stuck between a Windows box that isn't mine (but I have an admin account on) and a Mac, and I still have to read the Git documentation (as I'm not too familiar with Git, so I'll need to research the import - but I'm more than willing to perform the CVS to Git import!)
Quoted 33 lines · Mario Frasca
I know there is a way to export a complete CVS repository with history to git as I did so recently for an other project also on sourceforge (csvjdbc), I can't remember much more than it was an extension to git, but google for it and you will surely find it.
if it was me doing the transition, I would definitely keep the cvs
history: I would either construct and publish a git repository that holds the full cvs history of elks and remove the csv server. as a second choice I would keep the cvs server in its place but make it read-only.YMMV
MFQuoted 6 lines · 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?
Quoted 8 lines
Quoted 7 lines · Kirn Gill
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?
Quoted 4 lines
--
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
--
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
Quoted 4 lines · Mario Frasca
I know there is a way to export a complete CVS repository with history to git as I did so recently for an other project also on sourceforge (csvjdbc), I can't remember much more than it was an extension to git, but google for it and you will surely find it.
I imported a big CVS repo into hg a little while ago. I think it wins the award for the earliest timestamp on Sourceforge:
http://tack.hg.sourceforge.net/hgweb/tack/tack/log/4bea19e501ed
I bring this up because the CVS repository had lots of subtle corruptions inside and I had to do a fair bit of manual tweaking before it would import. (IIRC some files had been moved to Attic but there were still outstanding pointers to the old files elsewhere.) To do this I had to copy the whole repo database locally, rather than doing the import directly from the remote server.
Signature · 4 lines
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ "I have always wished for my computer to be as easy to use as my │ telephone; my wish has come true because I can no longer figure out │ how to use my telephone." --- Bjarne Stroustrup
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.
Quoted 18 lines · 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?
Quoted 7 lines · Kirn Gill
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
I'm migrating everything myself now; you can all rest easy, I'll handle this(TM)! :-)
Jody Bruchon
Quoted 11 lines · Harley Laue
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.gitI also have elkscmd.git, elksnet.git,& elksutils.git from the same base URL.