On Thu, Jul 5, 2012 at 9:22 AM, Cunningham, Robert <
[email protected]> wrote:

>  I had started thinking along similar lines, and I just realized that git
> seems to be becoming a vital utility for Fossil.  The export/import cycle
> appears to be useful in multiple scenarios encountered by Fossil users.
> There has also been much discussion about adding git-like features to
> Fossil.****
>
> ** **
>
> Would it be useful to think of Fossil becoming a git fork, where the core
> git functionality (at the capability level) is sandwiched between a
> low-level database and the high-level Fossil UI?
>

I see the fast export as a last resort for tough problems. I never
routinely go back and forth.


> If Fossil and git get any closer, they’ll be family.****
>
> **
>

As others have pointed out there are some pretty substantial differences in
philosophy and convergence seems unlikely. I would say appreciate each tool
for it's unique qualities and use the one that is best for you. To attempt
to straddle two worlds will probably be painful. I've done bridges between
various SCM's in the past and would say that it just generally isn't worth
the pain and risk.


>  **
>
> Thoughts?****
>
> ** **
>
> -BobC****
>
> ** **
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Matt Welland
> *Sent:* Thursday, July 05, 2012 8:33 AM
>
> *To:* Fossil SCM user's discussion
> *Subject:* Re: [fossil-users] How do I rebuild my fossil repo?****
>
>  ** **
>
> ** **
>
> On Thu, Jul 5, 2012 at 1:02 AM, Stephan Beal <[email protected]>
> wrote:****
>
> The only way i can think of is to dump/import the sql. ****
>
> Sorry for the brevity - typing on a phone on an over-full train.****
>
> ** **
>
> I think that dumping to a git fast export format and then writing scripts
> to manipulate the fast import data or importing to git, doing what needs to
> be done, then re-importing to fossil might be a good strategy for what you
> want. It won't help you with the tickets or other fossil specific data. I
> believe it is a loss-less process. I was able to slice and dice a large
> number of monotone db's into fossil db's using this approach.****
>
>  ****
>
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal****
>
> On Jul 5, 2012 7:52 AM, "Mohd Radzi Ibrahim" <[email protected]> wrote:***
> *
>
> ** **
>
> 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****
>
>
> _______________________________________________
> 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