On Sun, Mar 26, 2017 at 2:56 PM, <fossil-users-requ...@lists.fossil-scm.org> wrote:
> > Date: Sun, 26 Mar 2017 20:50:38 +0200 > From: Jan Danielsson <jan.m.daniels...@gmail.com> > To: fossil-users@lists.fossil-scm.org > Subject: Re: [fossil-users] GitLab v. Fossil. Was: Eric Raymond > (a.k.a. ESR) has published an SCM > Message-ID: <45ad044c-1bcd-3a67-bfb3-4e06688d9...@gmail.com> > Content-Type: text/plain; charset=utf-8 > > On 03/26/17 19:18, Richard Hipp wrote: > [---] > > (i) With Fossil, one can click on two nodes of the graph to see a > > diff between those two nodes. With GitLab, you apparently have to go > > to the separate "Compare" screen, then many type in (or paste in) hash > > name prefixes of the two check-ins you want to compare. This seems > > rather clumsy. But maybe I'm missing something. > > This is the same in Bitbucket. > ... > Anyway, I searched around to see if it was available in an alpha > version or something somewhere, and quickly realized others wanted the > feature as well. However, no good news on that front: The idea was > apparently "No, you use tool X for that.". (As it happens, this tool X > was a desktop application for the local checkout, which - in my mind - > kind of defeated the purpose). > To be fair, Bitbucket, github and gitlab are hosting services for a tool that is otherwise run on the local user's PC. those services focus on features more directly related to repository hosting than to a developer's versioning operations, which are done on the user's PC. Fossil, however, has a built-in GUI. Even though that GUI is based on web technology (so is remotely operable), it is still the primary GUI for the local user. As such, it is natural for it to provide features more expected in a desktop application than in a web application. In many ways, chiselapp.com is much simpler than gitlab.com et al, but Fossil itself provides features for interacting with individual repositories so chiselapp gets those features for "free", Maybe this is tangentially related to the cathedral vs bazaar > discussion; with Fossil, you typically have a central point where "all" > the useful checkins end up. > Most projects using a DVCS, whether Fossil, git, Hg or other, have a master repository. However, it is possible to use a DVCS in a peer-to-peer style, where, typically, each of the core developers maintains a "co-master" repository for the project. Fossil's own master repository is actually 3 (last I read) co-equal repositories that are periodically sync'ed with each other. Granted those 3 repositories are owned and controlled by the primary developer, it still illustrates the concept of peer-to-peer operation.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
