Richard Hipp wrote:
James Moger's circular timeline nodes and colored timeline graphs are
easily selectable "skin" options available to skin designers. For a
comparison:
http://www.fossil-scm.org/fossil/timeline?y=ci
http://www2.fossil-scm.org/fossil/timeline?y=ci
I hope you aren't too atta
On 30 March 2015 at 17:39, j. van den hoff wrote:
> a marginal point, but in case you care: the german word for
> repository/deposit actually is "Lagerstätte" where the diacritical mark over
> the `a' really matters. but "Lagerstatte" sounds really awful (since the "a"
> is pronounced like the "u"
>> * Access the Fossil repositories through Git protocol (readonly).
>
> Intellectually interesting, but, for me, not a selling point as I only use
> Git when I have to.
There are lots of software and services that support Git out of the
box (e.g., CI services, Go's packages, Rust's crates, Ruby's
+1 circular nodes, +1 colored lines, seemed to make visually tracking the
branch easier to my eyes. but as Brad said, a matter of style.
On Mon, Mar 30, 2015 at 2:22 PM, bch wrote:
> +1 circular "nodes", -1 colored lines, as a matter of style, imo.
> Really nice work, though!
>
> -bch
>
>
> On
Yes, I find file filtering useful too. Even better, it should be incorporated
in search drop-down list. FWIW, I manage now by ' f sett manifest on' and
grepping the manifest file.
Apart from common scenarios (don't remember the file name exactly, multiple
same/similar file names) you've men
+1 circular "nodes", -1 colored lines, as a matter of style, imo.
Really nice work, though!
-bch
On 3/30/15, Richard Hipp wrote:
> James Moger's circular timeline nodes and colored timeline graphs are
> easily selectable "skin" options available to skin designers. For a
> comparison:
>
>
James Moger's circular timeline nodes and colored timeline graphs are
easily selectable "skin" options available to skin designers. For a
comparison:
http://www.fossil-scm.org/fossil/timeline?y=ci
http://www2.fossil-scm.org/fossil/timeline?y=ci
--
D. Richard Hipp
d...@sqlite.org
_
On Sat, Mar 14, 2015 at 7:24 PM, Richard Hipp wrote:
> On 3/14/15, Ron W wrote:
> >
> > The key difference is that, in git, the puller can force the in coming
> > commits to be remapped into branches of their own. That is, I could
> commit
> > my changes to "trunk" in my clone, then when the oth
On Mon, Mar 30, 2015 at 6:50 AM, Vikrant Chaudhary
wrote:
> Hello everyone,
>
> I've been working on a project named "Lagerstatte", a front-end for
> Fossil repositories.
>
Looks interesting.
>
> Features that you can evaluate today:
>
> * Navigating through files.
> * Viewing latest revision o
a marginal point, but in case you care: the german word for
repository/deposit actually is "Lagerstätte" where the diacritical mark
over the `a' really matters. but "Lagerstatte" sounds really awful (since
the "a" is pronounced like the "u" in the English word `up', while the "ä"
is similar
Minor grammatical correction in last email:
s/Stephan and me/Stephan and I/
On 30 March 2015 at 16:20, Vikrant Chaudhary wrote:
> Hello everyone,
>
> I've been working on a project named "Lagerstatte", a front-end for
> Fossil repositories. The browser facing part is written in Ember.js,
> while
On Mon, Mar 30, 2015 at 6:47 AM, Oliver Friedrich <
redtalonof+mailingl...@gmail.com> wrote:
> Does fossil support ipv6?
> If it does, does it need extra compile-settings or is it supportet by
> default?
>
>
Fossil supports IPv6 in its default configuration.
I have IPv6 at my office. So most of
Hello everyone,
I've been working on a project named "Lagerstatte", a front-end for
Fossil repositories. The browser facing part is written in Ember.js,
while server runs a Ruby on Rails application which acts as a JSON
endpoint. Access to Fossil database is provided by Stephan's excellent
libfoss
Does fossil support ipv6?
If it does, does it need extra compile-settings or is it supportet by
default?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
14 matches
Mail list logo