On Fri, Jan 23, 2009 at 7:32 AM, TK Soh <[email protected]> wrote: > On Fri, Jan 23, 2009 at 6:21 AM, Peter Arrenbrecht > <[email protected]> wrote: >> On Fri, Jan 23, 2009 at 12:40 AM, TK Soh <[email protected]> wrote: >>> On Thu, Jan 22, 2009 at 4:08 PM, Peter Arrenbrecht >>> <[email protected]> wrote: >>>> I just went ahead and gave you push rights to >>>> >>>> http://bitbucket.org/parren/thg-hg-crew-tip/overview/ >>>> >>>> -parren >>> >>> Speaking of your repo, actually the 'hg-crew-tip' branch created in >>> your repo has been bugging me a little. Admittedly, I don't know much >>> about branches, and I personally have not come to appreciate the >>> importance of them in our model (obviously I'm very much a plain >>> one-clone-per-development kind of person ;-). So for now, I wonder if >>> you'd mind removing the branch from your repo somehow. >> >> Hmm. Since you already pulled some of my changes, the branch is in >> thg-crew anyway (albeit inactive at the moment). So if at all > > I know. I only realized that when it was a little too late. > >> necessary we could agree to push subsequent fixes in my repo on the >> default branch, thus deactivating the branch again there too. >> >> On the other hand, the branch allows me to do such things as `hg log >> -b hg-crew-tip` to see what I did for hg-crew vs the regular thg >> changes, even after I've pulled and merged newer versions of thg. >> >> But I'm OK either way. Dropping the branch would give me a reason to >> start playing with bookmarks. > > Probably good.
So I take it as agreed that we drop the branch on the next commit. -parren ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
