> Git rebase help has a very good graphic to explain what it does: > > Assume the following history exists and the current branch is "topic": > > A---B---C topic > / > D---E---F---G master > > From this point, the result of either of the following commands: > > git rebase master > git rebase master topic > would be: > > A'--B'--C' topic > / > D---E---F---G master > > Here, git forgets versions A, B & C if they are not published (tagged). > I agree we don't want fossil to forget anything. > > However, if fossil can do following, that would be very helpful: > > A---B---C topic > / > / A'--B'--C' (new name) > / / > D---E---F---G trunk > > - Altu >
But why would anyone want to do that? E. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
