Jim Meyering <[EMAIL PROTECTED]> writes: > I'm using git for projects I control, and find that I am less and less > tolerant of the abysmal (by comparison) performance of CVS and SVN
Git is enticing, but the main issue that's prevented me from adopting it has been the (apparent) clumsiness of maintaining tag information in conjunction with a "remote shared" repository. It's a bit hard to describe, but basically I want a single central git repository (for myself in this case, but something similar might be desirable for a project like Emacs) with multiple "branches" in it, and I want to be able to have different "checkouts" of that (e.g., a checkout of 'tag FOO'). When I make a change locally, I want to then commit the changes to the branch described by 'tag FOO' and _update the central repository's notion of 'tag FOO'_. The latter point seems to be where the problems occur. It's never entirely clear what goes wrong -- it always kinda-sorta works at first, but I always seem to end up inadvertently trashing the remote repository at some point (I think after merging back and forth between branches a bit), in confusing and hard to describe ways; this is not comforting. My vague impression is that working this way is possible, but not entirely trivial, and that other projects trying to use a similar model (x.org?) use big .git-config files specifying the proper tag synchronization to use, which seems kind of fragile. Sorry if that's not described well, my experience with git is somewhat limited. -Miles -- Do not taunt Happy Fun Ball. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
