Major Description
See also http://mail-archives.apache.org/mod_mbox/subversion- users/201006.mbox/%3CAANLkTik5AQ_eBSaBIUyLHXfFkuv6DZYO- rxJzmv0IcnL@mail.gmail.com%3E I have a long-running topic branch, which I have repeatedly reintegrated (into trunk). The topic is revived after each reintegration by merge --record-only to tell topic to ignore the reintegration revision on trunk. Observed: This produces so much duplication in log -g as to render the feature worthless. I will attached a bash script to reproduce what I am observing. Expected: log -g should be *a lot* smarter about filtering out duplicate entries. If that's not possible, log -g should support a --depth option to limit the insanity. If that's not possible, the Subversion Book should containg big red warning against using the --record-only strategy to revive topic branches.
Original issue reported by bpsm