On Tue, Oct 23, 2007 at 10:28:46PM +0200, Matthias Kestenholz wrote: > Hi, Hi, > If someone tracks the main branch you are working on and fetches > while you are travelling home, he has the WIP commit as a new tip > in his tree. > If he bases further work upon the WIP commit, he'll need to rebase > or merge his changes onto your new tip once you have amended or > replaced the commit. If you are working on the > master branch, you should really avoid rewinding it. Rewinding topic > branches is ok, but a temporary branch is still better to clearly tell > potential fetch-ers that this is only Work in Progress, and not meant > to be published in the current state. Good point. Although I guess if some workflow lets you directly hack on a public branch, it can have lots of other issues beyond just the WIP being pulled accidentally, no? Cheers. -- Jing Xue - 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
