On Thu, Jul 5, 2012 at 12:17 PM, <[email protected]> wrote:

> With help of some scripting and SQL, you can find all UUIDs for files that
> you want to remove and shun them. after that when you rebuild, your repo
> file will be shrunk.
>
> It is a bit effort though.
>
>
Could somebody point out to the documentation of internal table structure
and their relationship?



>
> > ----- Original Message -----
> > From: Stephan Beal
> > Sent: 07/05/12 09:15 AM
> > To: Fossil SCM user's discussion
> > Subject: Re: [fossil-users] How do I rebuild my fossil repo?
> >
> > Nothing can be removed from fossil. Ever. There is no way to shrink a
> repo,
> > only to re-create it with the desired files.
> > On Jul 5, 2012 2:54 AM, "Mohd Radzi Ibrahim" <[email protected]> wrote:
> >
> > > Hi,
> > >
> > > My problem is that when I started using fossil, there are so many
> unwanted
> > > files getting added my repository. Now, my repository database has
> already
> > > grown to 700mb. Some files were data files which were accidentally
> added by
> > > using addremove. My searching points to 'shun'; but it is impossible,
> since
> > > I could not find artifact that could be shunned. And painful, even if I
> > > found those files, since it could be numerous. What I want to do is to
> get
> > > a clean repo with current files I have in my checkout folders, with all
> > > tickets and historical events for those files.
> > >
> > > Thank you for any help rendered.
> > >
> > > best regards,
> > > Radzi.
> > >
> > > _______________________________________________
> > > fossil-users mailing list
> > > [email protected]
> > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> > >
> > >
> >
>
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to