Re: [sqlite] Move to Github!!?

On Dec 27, 2017, at 1:49 PM, Bob Friesenhahn wrote: > > Any DVCS is going to cause a penalty when the goal is to check out a > particular version of the files from a remote server …the first time. After you’ve got a clone, operations are usually much faster with

Re: [sqlite] Move to Github!!?

On Wed, 27 Dec 2017, Simon Slavin wrote: I understand that ZFS does this too, though I’ve never used ZFS. ZFS currently clones on the filesystem level. Filesystems are easy to create/delete and only consume the space required. Once a filesystem has been cloned, then only modified file

Re: [sqlite] Move to Github!!?

On 12/27/17, 2:23 PM, "sqlite-users on behalf of Simon Slavin" wrote: > Fair point. Automatic de-duplication would be more beneficial. And it > wouldn’t require extreme cleverness to be separately written into

Re: [sqlite] Move to Github!!?

On 27 Dec 2017, at 8:10pm, Warren Young wrote: > It is almost certainly the case that some of the files in x and y are > identical so that those files could be cloned from those in the other at the > filesystem level by making one of these OS-specific API calls, but it

Re: [sqlite] Move to Github!!?

On Dec 27, 2017, at 11:14 AM, Simon Slavin wrote: > > On 27 Dec 2017, at 4:05pm, Warren Young wrote: > >> DVCSes...by their very nature...want to clone the entire history of the >> whole project to every machine, then make a second copy of the tip of

Re: [sqlite] Move to Github!!?

On 27 Dec 2017, at 6:49pm, Peter Da Silva wrote: > On 12/27/17, 12:14 PM, "sqlite-users on behalf of Simon Slavin" > slav...@bigfraud.org> wrote: > >> Would running git/fossil on a filesystem like that

Re: [sqlite] Move to Github!!?

On 12/27/17, 12:14 PM, "sqlite-users on behalf of Simon Slavin" wrote: > Would running git/fossil on a filesystem like that solve the problem ? You would have to modify it to use the new APIs for things like

Re: [sqlite] Move to Github!!?

On 27 Dec 2017, at 4:05pm, Warren Young wrote: > Fossil has that problem, too. Most DVCSes do, because by their very nature, > they want to clone the entire history of the whole project to every machine, > then make a second copy of the tip of each working branch you

Re: [sqlite] Move to Github!!?

Hi, On Wed, Dec 27, 2017 at 12:00 PM, Warren Young wrote: > On Dec 27, 2017, at 7:49 AM, Nelson, Erik - 2 > wrote: >> >>> Also when you're forced to use a third party ticket system, fossil i >>> missing one of its big advantages. >> >> I'm

Re: [sqlite] Move to Github!!?

On 27 Dec 2017, at 1:51pm, Fredrik Gustafsson wrote: > - What are our demands for a ticket system, would fossil or gitlab (for > example) suit us better? Here’s something from experience. You can have three types of ticket: A) Internal tickets. These are raised by employees

Re: [sqlite] Move to Github!!?

On Dec 27, 2017, at 7:49 AM, Nelson, Erik - 2 wrote: > >> Also when you're forced to use a third party ticket system, fossil i missing >> one of its big advantages. > > I'm no Fossil expert, but it does seem to have a ticketing system. Is there > something

Re: [sqlite] Move to Github!!?

On Dec 27, 2017, at 3:23 AM, Rob Willett wrote: > > I know RCS is possibly older than the average reader on this mailing list, > but it works very well for us and the workflow 'just works’. Fossil “just works” for me, too. I’m curious why Subversion never

Re: [sqlite] Move to Github!!?

While this is really entirely derailed I'll add... If monotone wasn't dead 6 years now I'd be using that...but it doesn't support unicode filenames very well; and they haven't wanted to do updates. I was really resistant to migrating to Git; actually almost any other alternaitve of them.

Re: [sqlite] Move to Github!!?

Fredrik Gustafsson Sent: Wednesday, December 27, 2017 8:52 AM >Ask yourself if you want a system that is easy to use or easy to learn. That feels like a false choice- why can't it be both easy to learn and easy to use? That's a hallmark of good engineering. >Also when you're forced to use a

Re: [sqlite] Move to Github!!?

Hi, I'm a former git developer and have been lurking on this maillist (since I work with sqlite3) and followed fossil (since I'm interested in scm). On Wed, Dec 27, 2017 at 10:23:57AM +, Rob Willett wrote: > the commands were exceptionally confusing. It appeared to us that most of > the

Re: [sqlite] Move to Github!!?

Dear all, I've enjoyed reading about the Github vs Fossil discussion. There's been some passionate and provocative statements :) What its done for me is make me think again about how we manage our source code control which is always good. We very recently moved from our existing text based

Re: [sqlite] Move to Github!!?

On Tue 26 Dec 2017 2:09 PM, Warren Young wrote: > On Dec 26, 2017, at 2:47 AM, J Decker wrote: > > > > doesn't require a fee unless they want to amke it private. > > You’re speaking of today’s benevolent policies. > Yes, I completely agree with everything you said. Nicely

Re: [sqlite] Move to Github!!?

On Tue 26 Dec 2017 3:08 PM, Damien Sykes wrote: > Hi, > This is a question I have asked myself many times (I.E. Git projects moving > to Fossil). > GitHub is well known and boasts over 74 million repositories, yet Fossil, > which both hosts and utilises one of the most well-known database systems

Re: [sqlite] Move to Github!!?

On Dec 26, 2017, at 12:07 PM, Bob Friesenhahn wrote: > > On Tue, 26 Dec 2017, J Decker wrote: >>> Why aren't you moving all of your GitHub projects over to Fossil! >>> >> Because Pull Requests, and a larger variety of tools to deal with Git >> repositories. > >

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 3:31 PM, Keith Medcalf wrote: > > Heavens forbid! > > How is it possible to work if not from a Command-Line window? That is, > YUCK. > Seriously how can anyone get any work done at all without having a command > prompt at which one, how to put this,

Re: [sqlite] Move to Github!!?

ite-users- >boun...@mailinglists.sqlite.org] On Behalf Of Scott Doctor >Sent: Tuesday, 26 December, 2017 14:07 >To: sqlite-users@mailinglists.sqlite.org >Subject: Re: [sqlite] Move to Github!!? > > >What fossil needs is for the UI to perform ALL normal common >functions (new, commit, clone,...

Re: [sqlite] Move to Github!!?

On Dec 26, 2017, at 2:47 AM, J Decker wrote: > > doesn't require a fee unless they want to amke it private. You’re speaking of today’s benevolent policies. Let’s review: 1. SourceForge: Once the largest host of FOSS software, eventually became “evil” in the eyes of many of

Re: [sqlite] Move to Github!!?

What fossil needs is for the UI to perform ALL normal common functions (new, commit, clone,...) WITHOUT having to open a command line window. That is imo the main limitation. - Scott Doctor sc...@scottdoctor.com -

Re: [sqlite] Move to Github!!?

gt; >-Original Message- >> >From: sqlite-users [mailto:sqlite-users- >> >boun...@mailinglists.sqlite.org] On Behalf Of Bob Friesenhahn >> >Sent: Tuesday, 26 December, 2017 12:08 >> >To: SQLite mailing list >> >Subject: Re: [sqlite] Move to

Re: [sqlite] Move to Github!!?

On 26 Dec 2017, at 7:07pm, Bob Friesenhahn wrote: > On Tue, 26 Dec 2017, J Decker wrote: > >>> Why aren't you moving all of your GitHub projects over to Fossil! >> >> Because Pull Requests, and a larger variety of tools to deal with Git >> repositories. > > It is

Re: [sqlite] Move to Github!!?

me. > > >-Original Message- > >From: sqlite-users [mailto:sqlite-users- > >boun...@mailinglists.sqlite.org] On Behalf Of Bob Friesenhahn > >Sent: Tuesday, 26 December, 2017 12:08 > >To: SQLite mailing list > >Subject: Re: [sqlite] Move to Github!!? &g

Re: [sqlite] Move to Github!!?

>boun...@mailinglists.sqlite.org] On Behalf Of Bob Friesenhahn >Sent: Tuesday, 26 December, 2017 12:08 >To: SQLite mailing list >Subject: Re: [sqlite] Move to Github!!? > >On Tue, 26 Dec 2017, J Decker wrote: >>> Why aren't you moving all of your GitHub projects ov

Re: [sqlite] Move to Github!!?

On Tue, 26 Dec 2017, J Decker wrote: Why aren't you moving all of your GitHub projects over to Fossil! Because Pull Requests, and a larger variety of tools to deal with Git repositories. It is good that such tools are available to help surmount Git's extreme complexity. Are there such

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 5:10 AM, Richard Hipp wrote: > On 12/25/17, Shekhar Reddy wrote: > > > > Is there any particular reason that the source is not moved to GitHub? I > > think that would reach more number of people there. > > > > There is a

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 5:10 AM, Richard Hipp wrote: > > Finally, the use of GitHub would create a reliance on an outside > company over which we have no influence. The people who run GitHub > today seem like great folks. But the company might be sold or fall > under new

Re: [sqlite] Move to Github!!?

On Tue, 26 Dec 2017 10:27:39 -0500 "J. King" escribió: > I use Git, but I'm not attached to it. I run my own publicly-accessible > remote (using Gitea), but that would be completely replaceable with Fossil > (which I am very impressed by). > > What's not so easy to replace

Re: [sqlite] Move to Github!!?

On Tue, Dec 26, 2017 at 9:45 AM, Don V Nielsen wrote: > > What's not so easy to replace is the Git integration in my editor (Visual > Studio Code) > > Same here, but I use JetBrains products. I put a bug in the ear of > JetBrains. At least its something. > > Have a good

Re: [sqlite] Move to Github!!?

and submodules etc. Though it doesn't matter what VCS I use I always > >seem to > >come across, and struggle with, the concept of branching and merging! > >In any case, my incompetencies aside. People seem to be slowly moving > >away > >from SourceForge

Re: [sqlite] Move to Github!!?

;FossHub I actually thought that was an attempt to make a Fossil-based >GitHub. Seems that isn't the case after all. >Cheers. >Damien. >-Original Message- >From: Richard Hipp >Sent: Tuesday, December 26, 2017 1:10 PM >To: SQLite mailing list >Cc: shekharreddy.k.

Re: [sqlite] Move to Github!!?

To: SQLite mailing list Cc: shekharreddy.k...@gmail.com Subject: Re: [sqlite] Move to Github!!? On 12/25/17, Shekhar Reddy <shekharreddy.k...@gmail.com> wrote: Is there any particular reason that the source is not moved to GitHub? I think that would reach more number of

Re: [sqlite] Move to Github!!?

On 12/25/17, Shekhar Reddy wrote: > > Is there any particular reason that the source is not moved to GitHub? I > think that would reach more number of people there. > There is a mirror of the SQLite repository on GitHub at https://github.com/mackyle/sqlite

Re: [sqlite] Move to Github!!?

On Mon, Dec 25, 2017 at 8:24 PM, Jay Kreibich wrote: > > > On Dec 25, 2017, at 12:24 PM, J. King wrote: > > > > SQLite source is managed in a Fossil (not Git) repository, which is > software itself designed by Dr. Hipp and based on SQLite. GitHub would be >

Re: [sqlite] Move to Github!!?

> On Dec 25, 2017, at 12:24 PM, J. King wrote: > > SQLite source is managed in a Fossil (not Git) repository, which is software > itself designed by Dr. Hipp and based on SQLite. GitHub would be an entirely > inappropriate venue. > > SQLite is also not open source

Re: [sqlite] Move to Github!!?

On Mon 25 Dec 2017 11:49 PM, Shekhar Reddy wrote: > Hi, > > Is there any particular reason that the source is not moved to GitHub? I > think that would reach more number of people there. > So are you saying it would be the most used in the galaxy? SQLite is the most used database engine in the

Re: [sqlite] Move to Github!!?

25 December, 2017 11:19 >To: sqlite-users@mailinglists.sqlite.org >Subject: [sqlite] Move to Github!!? > >Hi, > >Is there any particular reason that the source is not moved to >GitHub? I >think that would reach more number

Re: [sqlite] Move to Github!!?

As stated, SQLite is managed by Fossil, and Fossil is managed by SQLite. (I think it was) Dr Hipp that stated that "Fossil is eating its own dog food". https://www.google.ca/search?q=eating+your+own+dog+food=utf-8=utf-8=firefox-b_rd=cr=0=SENBWvCGOs6fXo7ynMAJ

Re: [sqlite] Move to Github!!?

SQLite source is managed in a Fossil (not Git) repository, which is software itself designed by Dr. Hipp and based on SQLite. GitHub would be an entirely inappropriate venue. SQLite is also not open source software in the conventional sense. SQLite is written by a small team of people, and

[sqlite] Move to Github!!?

Hi, Is there any particular reason that the source is not moved to GitHub? I think that would reach more number of people there. Regards Shekhar ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org