On 24/07/2013, at 7:28 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> AFAIK git offers a mechanism for changing history, but Fossil doesn't like > for history to change. It isn't changing history, it is setting a subproject free to live it's own life. That's not an unusual situation, given that projects often grow and then divide. So I detach a local repository, rename it, and continue with a new repository for the subproject. But it contains all of the history for the parent project, as does the parent project repository. I can push that to a branch and close it in the detached repo, no big deal. But it isn't ideal, especially if the original repo is large. Being able to detach based on a specific commit or branch would be nice (not essential, but nice). Steve _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
