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

simple cvs-like git wrapper

From
EPEd S. Peschko <esp5@pge.com>
Date
Jan 29, 2008, 20:40 UTC
Message-ID
<20080129204048.GA9612@venus>
hey all,

We've been trying out git here for a while now, and we've noticed two things that we both like and dislike: git's flexibility, and git's flexibility.

Git's flexibility is great in the sense that power users can basically bend git to their will, but its' flexibility is also causing workflow issues in our environment, where beginning users can get lost in all the options that it has, and this is causing communication issues for these folks with the rest of our team.

Hence, I was hoping that people could suggest ways of simplifying git, making a cvs-like frontend for people to use.

I was thinking of something like this:
gvs branch <branch name>: 
	creates a branch for people to start making edits on in their
	localized copy.
gvs commit:
	commits that branch to a centralized git repository.
gvs update:
    Takes the latest changes, from all branches, that everyone 
	else has committed into the centralized git repository, and merges 
	them onto the current branch. 
gvs list:
	lists all the branches that have been merged into the current
	workspace.

In other words, what I'm looking for is sort of 'cvs+'. Instead of working on one, synchronized branch as per cvs, we want to work on several, parallel, branches that synchronize on intervals.

We basically want this for managing related changesets - we want to be able to switch from one patch branch to another and commit them separately - but we don't want to sacrifice the automatic integration that you get from cvs by doing:

	cvs update
on a given branch.

Anyways, hope this makes sense. I'm not sure how feasible the above is - it's meant to be as simple it can be, with as much DWIM-ness as possible. Any feedback is appreciated.

Ed

( ps - We could just use CVS of course, but that's just too simple, with no easy way of managing which change goes along with which feature request... )

Next: Jakub Narebski
Message 1 of 15 in “simple cvs-like git wrapper”
  1. Ed S. PeschkoJan 29, 2008
  2. Jakub NarebskiJan 29, 2008
  3. Ed S. PeschkoJan 30, 2008
  4. Shawn O. PearceJan 30, 2008
  5. Ed S. PeschkoJan 30, 2008
  6. Shawn O. PearceJan 31, 2008
  7. Ed S. PeschkoJan 31, 2008
  8. Shawn O. PearceJan 31, 2008
  9. Junio C HamanoJan 31, 2008
  10. Daniel BarkalowJan 30, 2008
  11. Kate RhodesFeb 1, 2008
  12. Johannes SchindelinFeb 1, 2008
  13. Jakub NarebskiFeb 1, 2008
  14. Uwe Kleine-KönigFeb 1, 2008
  15. Jakub NarebskiFeb 1, 2008

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.