Hi On Wed, Aug 14, 2013 at 12:31:42AM -0400, Erik Schnetter wrote: > Coming back to the original issue: In a typical git workflow, "git > push" isn't the second half of a "git commit" that, when combined, are > equal to an "svn commit". In a git workflow, it makes a lot of sense > to push a whole repository, including all branches.
However, this is not intuitive. If I switched to a branch and push commits I expect to push only the commits that are applied to the branch I am currently at. I can see your point, but that's just not what someone who isn't already familiar with git would expect. Apparently even the git developers seem to have come to agree on that point. The 'simple' method will be default for git v2. And I think the argument "once you change your workflow git will be great" is the wrong way around at least partially. A useful tool doesn't force a workflow on me, it allows me to use the workflow I find useful without getting in my way. Of course there are cases in which a particular workflow is just bad practice to begin with (let's say, not using a version control system at all), but we probably don't have to discuss these cases. I just wish there would be some system that would keep simple things as simple as Subversion while still allowing complex situations like git; on the command line of course. But let's move on. Frank
signature.asc
Description: Digital signature
_______________________________________________ Users mailing list [email protected] http://cactuscode.org/mailman/listinfo/users
