tag:blogger.com,1999:blog-3888382143307542639.post9202139100767967131..comments2023-02-02T03:36:20.483+00:00Comments on Lacking Rhoticity: My workflow with git-cl + RietveldMark Seabornhttp://www.blogger.com/profile/08046205947658697263noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3888382143307542639.post-54833403167096345122011-02-16T15:42:37.781+00:002011-02-16T15:42:37.781+00:00You might also consider patching rietveld to bette...You might also consider patching rietveld to better handle sets of patches. You wouldn't have this problem if you could simply add later patches to rietveld's entry for an issue, and then rebase everything in the proper order before pushing.<br /><br />I'm also of the "no one needs to see your mistakes" camp that believes squashing microhistory is a *good* thing when working on large shared projects. I want a clean commit log that is easy to understand.C. Scott Ananianhttp://cscott.netnoreply@blogger.comtag:blogger.com,1999:blog-3888382143307542639.post-81392550683052832142010-09-02T17:39:59.740+01:002010-09-02T17:39:59.740+01:00Mercurial queues also look designed for this probl...Mercurial queues also look designed for this problem.MHnoreply@blogger.comtag:blogger.com,1999:blog-3888382143307542639.post-58317403555910609122010-08-20T21:47:26.779+01:002010-08-20T21:47:26.779+01:00Have you considered using Stacked Git or guilt? I...Have you considered using Stacked Git or guilt? It sounds like this is the sort of workflow those tools were designed for. I'm not sure how all those tools interact, though (git-svn, git-cl, Stacked Git).John Leenoreply@blogger.com