On 2009-04-28, martin f krafft <madduck@xxxxxxxxxxx> wrote: >> I know "tg depend" only has the "add" subcommand right now, >> but is there a manual way of getting the effect of a >> hypothetical "tg depend remove"? > > No, not yet, see http://bugs.debian.org/505303 for further > discussion on the issue. Yes, I'd seen that on a google search, and it made my head hurt :-) (My fault, not theirs...!) I was latching onto the last line of that email: "Maybe in your case this could be even simpler but this should be the general process". My situation _should_ be the simplest. Every topgit branch starts off from master, and they're all notionally independent of each other. As long as they're here, they're "cooking", all together, in a branch called t/all. When one branch is deemed to be cooked, a "tg export" takes that code to master, and I intend to delete t/all and create it afresh with the rest of the dependencies (the old set minus the one that finished cooking). I was hoping to hear if anyone sees any red flags in that strategy. Thanks again, Sitaram -- 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