Horst von Brand wrote: > Martin Langhoff <martin.langhoff@gmail.com> wrote: > > [...] > > >>In practice, a new developer will often roll up commits to avoid >>sending a string of shameful patches and corrections on top -- I often >>do that ;-) . Developers with more "mana" will have published repos >>where Junio pulls directly from -- and they get merged with full >>history. Of course -- they don't have brown-paper-bag commits like I >>do... > > > I bet they have a scratchpad on their laptop (full of brown-paper-bag > commits and backtracking) from which they push into a cleaned up repository > for public consumption. I just do a lot of branches. Incidentally though, is there any way to make a commit completely go away without resetting the files? It'd be a nice feature even if it can only do it from the top down, unlike git-revert which can do it anywhere in the middle as well. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed Nov 02 19:54:45 2005
This archive was generated by hypermail 2.1.8 : 2005-11-02 19:54:49 EST