Re: [fossil-users] how to delete old history?
Thank you all for the ideas. I'll have a look at shunning, if it could be used. I'll have a look at it. Best regards, Petr ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] how to delete old history?
Dear Fossil users, I have a several year old project that has been managed in several VCS over its lifetime, and for past year or two it has been managed using Fossil. The history of the project contains some ancient code that is not necessary now, but worse, it also contains some ancient binary library files, which make the history quite large. Is there a way how to abandon some old code, for example to delete every commit that is older than some date? I could export it to GIT, there make the change and import back, but this will change code commit hashes and therefore I'm not sure if it would be possible to keep the relations between tickets, commits and commit messages. Thank you, Petr Pudlak ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] how to delete old history?
On Wed, Jul 24, 2013 at 1:36 PM, Petr Pudlák petr@gmail.com wrote: Dear Fossil users, I have a several year old project that has been managed in several VCS over its lifetime, and for past year or two it has been managed using Fossil. The history of the project contains some ancient code that is not necessary now, but worse, it also contains some ancient binary library files, which make the history quite large. Is there a way how to abandon some old code, for example to delete every commit that is older than some date? Nope. Fossil's data is, by design, immutable. There is a mechanism called shunning to stop syncing of specific artifacts but that is intended for cases like wrongly licensed data, security-relevant information, etc., and is supposed to be a last resort. It not the right tool for what you want to do (fossil doesn't have a tool for that, by design). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] how to delete old history?
On Jul 24, 2013, at 13:36 , Petr Pudlák wrote: I have a several year old project that has been managed in several VCS over its lifetime, and for past year or two it has been managed using Fossil. The history of the project contains some ancient code that is not necessary now, but worse, it also contains some ancient binary library files, which make the history quite large. Is there a way how to abandon some old code, for example to delete every commit that is older than some date? I could export it to GIT, there make the change and import back, but this will change code commit hashes and therefore I'm not sure if it would be possible to keep the relations between tickets, commits and commit messages. Exporting to git was my first idea. If there are just a few of those big binary files, you can use shunning. Otherwise, I guess you'll need to script something using fossil deconstruct, but I have no experience with that route. Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] how to delete old history?
From my Fossil cheat sheet...regarding this mail thread: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg09584.html - fossil shunning or deleting files permanently. - Use the Admin - Shun page on fossil ui. Then enter the full SHA1 of the artifact to delete. Then use c:\myrepofossil rebuild --vacuum (The ui button did not work.) These deletions are only seen on the LOCAL repo and must be push|pull'ed manually. c:\myrepofossil config push shun \\mynetwork\myrepo.fossil c:\myrepofossil config pull shun \\mynetwork\myrepo.fossil Thanks for Fossil! On Wed, Jul 24, 2013 at 11:50 AM, Ramon Ribó ram...@compassis.com wrote: 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, Spainfax. +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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] how to delete old history?
True, that was already discussed in the attached thread. Some mentioned SQL dumps of artifacts, or you could open your repo in a SQLite browser to get the list. But, at least it works. Automating shuns is high on my list too! At least enable the cmd via fossil.exe and not just the ui? On Wed, Jul 24, 2013 at 12:18 PM, Steve Landers st...@digitalsmarties.comwrote: On 24/07/2013, at 11:06 AM, sky5w...@gmail.com wrote: From my Fossil cheat sheet...regarding this mail thread: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg09584.html - fossil shunning or deleting files permanently. - Use the Admin - Shun page on fossil ui. Then enter the full SHA1 of the artifact to delete. Then use c:\myrepofossil rebuild --vacuum (The ui button did not work.) These deletions are only seen on the LOCAL repo and must be push|pull'ed manually. c:\myrepofossil config push shun \\mynetwork\myrepo.fossil c:\myrepofossil config pull shun \\mynetwork\myrepo.fossil It not practical to individually manually shun each unwanted artifact thru the web interface. --Steve On Wed, Jul 24, 2013 at 11:50 AM, Ramon Ribó ram...@compassis.com wrote: 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, Spainfax. +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 ___ 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
