Yes, that would be the idea, giving the possibility to define an initial date, a branch selection, etc. ---- Compass Ing. y Sistemas Dr. Ramon Ribo http://www.compassis.com ram...@compassis.com c/ Tuset, 8 7-2 tel. +34 93 218 19 89 08006 Barcelona, Spain fax. +34 93 396 97 46
2013/7/24 Isaac Jurado <dipto...@gmail.com>: > On Wed, Jul 24, 2013 at 4:21 PM, Steve Landers > <st...@digitalsmarties.com> wrote: >> >> 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). > > That looks like a Fossil to Fossil export/import feature, without having > to go through Git fast-export format, right? > > -- > Isaac Jurado > > "The noblest pleasure is the joy of understanding" > Leonardo da Vinci > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
