On Thu, Jun 19, 2008 at 01:54:15PM -0700, Junio C Hamano wrote: > If you have a history of this shape: > > (other cruft) > \ > ----o---o next > / > o---o---o---o master > / / > ---o---o---A > > which "branch label" would you give to the format-patch output that shows > commit A? It may apply to both master and next, and it is really up to > the project's convention what to do with it. The side branch the patch > was developed on may be named "quick-hack", which would not have any > relevance to the final location of where that patch wants to be in. I follow what you are saying. In our workflow case, pointing out the remote (public) branch name should be sufficient (as this's the public shared branch among us, and all patchsets shared with others are against the public branches). Perhaps I can add it to the [PATCH] text in the subject line as Jeff suggests. My problem is that I can't send a patch out to the list for other developers to try, without some annotation for them, of which branch to try it on. Mukund -- 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
