On Thu, Mar 25, 2010 at 4:51 PM, Tyler Roscoe <ty...@cryptio.net> wrote:
> You should look at your branch's ancestry to make sure those revisions > are not needed. If they're not, you can use a --record-only merge to > make the branch think it has those revisions. Subsequent merges from > trunk should then skip over those revisions and merge only what you > want. I see. Could you help with the command that is needed here? Never did that before. Is there something we can do in trunk so that subsequent new branches do not need to do the same?
