Ramkumar Ramachandra wrote: > Right, so you can just squash them. Also, I think I'm sending in > patches too fast so I'll slow down and rebase them on top of `pu` > every time. Thank you for this. FWIW I find it useful when discussing a piece of code or documentation to bounce back and forth multiple versions of small fragments. Then once the discussion has settled down, it can be useful to see the big picture again, with the new changes incorporated. If you want to make sure the latest version of a patch is always available, that is a noble goal, too, but I think a frequently- rebased public branch for your patch series is a better way to achieve that. Unrelated: in case you are interested, the git-resurrect.sh script from contrib can extract topic branches from pu, if you want to see Junio’s topic branch for your patch. Cheers, Jonathan -- 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