Activity log for bug #886542
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2011-11-05 13:06:52 | Kirill Müller | bug | added bug | ||
| 2011-11-05 14:42:34 | Jelmer Vernooij | bzr-rewrite: status | New | Incomplete | |
| 2011-11-05 19:53:12 | Kirill Müller | attachment added | Unix shell script to reproduce the behavior https://bugs.launchpad.net/bzr-rewrite/+bug/886542/+attachment/2586598/+files/test.sh | ||
| 2011-11-07 10:00:24 | Jelmer Vernooij | bzr-rewrite: status | Incomplete | Triaged | |
| 2011-11-07 10:01:49 | Jelmer Vernooij | description | Sometimes I have the following use case: ---A----A' \ B----C I need to rebase both B and C against A'. This occurs after rebasing B against A' (--> B') and C against B': ---A----A' \ B'----B----C In the best case, the commits of B against B' are useless. In the worst case, conflicts are generated, which become pointless commits if resolved. I understand that this is by design; however, an option to suppress pointless commits during rebase would be great here. Or could we even, by default, ignore pointless commits with exactly one parent? | It would be nice if bzr-rewrite supported skipping empty revisions during rebase. | |
| 2011-11-07 10:02:27 | Jelmer Vernooij | description | It would be nice if bzr-rewrite supported skipping empty revisions during rebase. | It would be nice if bzr-rewrite supported skipping empty revisions during rebase. This will require a fair bit of refactoring though, as it means we can't plan the full rebase operation up front. | |
| 2011-11-07 10:02:30 | Jelmer Vernooij | bzr-rewrite: importance | Undecided | Medium | |
| 2012-08-30 15:42:35 | Samuel Bronson | bug | added subscriber Samuel Bronson |
