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...
)
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
