git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Qgit performance and maintain CVS environment with GIT repository

From
JWJan Wielemaker <wielemak@science.uva.nl>
Date
Oct 19, 2007, 10:34 UTC
Message-ID
<200710191234.47944.wielemak@science.uva.nl>
In-Reply-To
<471871BD.7030608@bluelane.com>
On Friday 19 October 2007 10:58, Pete/Piet Delaney wrote:
Show 15 quoted lines
> Jan Wielemaker wrote:
> > On Friday 19 October 2007 02:22, Pete/Piet Delaney wrote:
> >> We are definitely not fine with CVS, the branch merging isn't
> >> comfortable. I'm just wondering about maintaining the existing
> >> CVS browsers and the build scripts if it's not a big deal. I'll
> >> try the git-cvsserver path. If anyone has any war stories to share
> >> on the path this would be an ideal time to share them.
> >
> > As for web browsing the history, our project was quickly convinced
> > gitweb is a lot better than cvsweb.  We are starting to get use to
> > basic git.  One developer works on CVS.  This is a bit handicapped,
> > but workable after a few patches to git-shell and git-cvsserver.
>
> Could you tell me a bit more about those patches and the need for using
> git-shell (haven't even messed with that yet).

One patch concerned handling "cvs update -p", which was accepted and I guess will end up in the stable version someday. One concerned handling "cvs diff -c", which I never submitted. I first tried a more general approach to get diff option processing complete, but I had to backtrack on that. Now I have a quite simple hack, but more complete coverage of diff option processing requires a bit more perl knowledge than I have.

I submitted a patch for shell.c to make it call "git cvsserver server" if a commandline "cvs server" was passed to it, so you can do CVS+SSH compatible to normal CVS. I got so many comments I decided to keep it for myself for now.

> I don't think we need to have any developers continuing to use CVS;
> but I may be wrong. I think I read that there's a limitation to being
> on the main branch and unfortunately most of out tags are on a release
> branch.
No, you can checkout any GIT branch as it it were a CVS module.
	--- Jan
Previous: Pete/Piet DelaneyNext: Andreas Ericsson
Message 33 of 39 in “How to Import a bitkeeper repo into git”
  1. free cycleJul 9, 2007
  2. VMiklosJul 9, 2007
  3. Linus TorvaldsJul 9, 2007
  4. Pete/Piet DelaneyOct 15, 2007
  5. Shawn O. PearceOct 16, 2007
  6. Pete/Piet DelaneyOct 16, 2007
  7. David BrownOct 16, 2007
  8. Linus TorvaldsOct 16, 2007
  9. David BrownOct 16, 2007
  10. Linus TorvaldsOct 16, 2007
  11. Pete/Piet DelaneyOct 16, 2007
  12. Marco CostalbaOct 16, 2007
  13. Pete/Piet DelaneyOct 16, 2007
  14. Marco CostalbaOct 16, 2007
  15. Andreas EricssonOct 16, 2007
  16. Marco CostalbaOct 17, 2007
  17. Andreas EricssonOct 17, 2007
  18. Pete/Piet DelaneyOct 17, 2007
  19. Marco CostalbaOct 17, 2007
  20. Pete/Piet DelaneyOct 17, 2007
  21. Pete/Piet DelaneyOct 17, 2007
  22. Marco CostalbaOct 17, 2007
  23. Robin RosenbergOct 17, 2007
  24. Marco CostalbaOct 17, 2007
  25. Robin RosenbergOct 18, 2007
  26. Pete/Piet DelaneyOct 18, 2007
  27. Johannes SchindelinOct 19, 2007
  28. Pete/Piet DelaneyOct 19, 2007
  29. Jeff KingOct 19, 2007
  30. Johannes SchindelinOct 19, 2007
  31. Jan WielemakerOct 19, 2007
  32. Pete/Piet DelaneyOct 19, 2007
  33. Jan WielemakerOct 19, 2007
  34. Andreas EricssonOct 19, 2007
  35. Pete/Piet DelaneyOct 19, 2007
  36. Andreas EricssonOct 19, 2007
  37. Jan HudecOct 16, 2007
  38. Linus TorvaldsOct 16, 2007
  39. Johannes SchindelinNov 6, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.