On Fri, Mar 06, 2009 at 11:58:36AM -0500, Peter Harris wrote: > On Fri, Mar 6, 2009 at 11:10 AM, Josef Wolf wrote: > > On Thu, Mar 05, 2009 at 02:48:14PM -0500, Peter Harris wrote: > >> > >> True, but in my experience it happens considerably less often with > >> git. I find and fix most of my typos when reviewing my change-set > >> before doing a "git push" or "git svn dcommit". > > > > So you are rewriting yourself but not accept rewrites by svn ;-) > > No, I am not rewriting myself *after I publish*. I see the smiley, but > I think you missed the point. > > "git push" or "svn ci" is the end of the rewrites. I see. Thanks for the clarification! > >> Indeed. Or even not-so-random names, such as cloneX/topic-name if you > >> prefer. > > > > That would have the risk of multiple clones pushing to the same branch. > > Only if cloneX pushes to cloneY/topic-name. Does each clone not have a > unique name? I'd rather not rely on the clones having unique names. > > Does that look sane? > > No. But it doesn't look any more insane than any other workflow > involving Subversion that I can think of. :-) OK, I parse that as "there's not much room for improvement" :-) Thanks for your great help! I have learned a lot in this thread! -- 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
