On 02/02/2017 11:11 AM, oldk1331 wrote: > The solution is to use feature branch and rebase > (and then push --force). When you successfully > carry out a rebase, you'll know how it works and > can't live without it. And you will no longer need > a separate repo fricasAlgTop.
Exactly. A second repo is completely unnecessary with git. Martin, it's really worth it to learn how rebase works. You can use this to clean up patches, reorder them or even join or split patches to get a cleaner history. Git offers (at least) two things. 1) Commit commit commit, in order to have a private history of how things develop. 2) Use git rebase -i in order to clean up the whole mess of wild development history before you show your new stuff to the public. Qian, I have several feature branches on top of trunk, in fact a whole tree with (sub-)branches that sit on top of one of my feature branches). By chance, do you happen to know how I can rebase (with just one command) the whole tree? Ralf -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/fricas-devel. For more options, visit https://groups.google.com/d/optout.
