Never mind. I swapped ubg & brbg
> - Original Message -
> From: Altu Faltu
> Sent: 07/23/11 12:01 PM
> To: fossil-users@lists.fossil-scm.org
> Subject: Re: [fossil-users] Automatic branch color selection. Was: Question
> on short-lived branches in fossil
>
> Why does the same branch (tr
Why does the same branch (trunk) take different backgrounds?
- Original Message -
From: Richard Hipp
Sent: 07/23/11 04:55 AM
To: fossil-users@lists.fossil-scm.org
Subject: [fossil-users] Automatic branch color selection. Was: Question on
short-lived branches in fossil
On Fri, Jul 22, 2
On Fri, Jul 22, 2011 at 7:25 PM, Richard Hipp wrote:
>
> Feedback is encouraged. Remember this changes is experimental and might
> disappear at any moment!
Looks very nice. The pastel colors do a great job on white with black
text. I'd say a worthwhile feature. Is there an easy way to make that
At 04:25 PM 7/22/2011, Richard Hipp wrote:
>An experimental change to implement this is on the server...
>
>I tried Ross's proposed color choosing algorithm but it didn't
>work out. So instead I used the hash to select a Hue in an HSV
>color space, held the S and V fixed, and mapped the resul
On Fri, Jul 22, 2011 at 7:25 PM, Richard Hipp wrote:
>
>
> On Fri, Jul 22, 2011 at 5:32 PM, Stephan Beal wrote:
>
>> On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig wrote:
>>
>>> For skins that are dark text on white background, then using the
>>> existing MD5 hash on the tag name, picking a conv
On Sat, Jul 23, 2011 at 1:25 AM, Richard Hipp wrote:
> An experimental change to implement this is on the server. Add the "brbg"
> query parameter to the timeline method to have the background color set by
> branch name. Add "ubg" to have the background color set by user name.
> Examples:
>
>
On Fri, Jul 22, 2011 at 5:32 PM, Stephan Beal wrote:
> On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig wrote:
>
>> For skins that are dark text on white background, then using the
>> existing MD5 hash on the tag name, picking a convenient three;
>>
> ...
>
> it would make an entertaining experime
On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig wrote:
> For skins that are dark text on white background, then using the
> existing MD5 hash on the tag name, picking a convenient three;
>
...
it would make an entertaining experiment, whether or not it turns out to be
useful in practice.
--
---
At 12:14 PM 7/22/2011, Richard Hipp wrote:
>On Fri, Jul 22, 2011 at 3:07 PM, Ross Berteig
> wrote:
>
>> It would be nice if branches had a default color distinct from
>> the trunk. ... One way to do that that *might* be ... generate a
>> hash of the branch tag name and use it for the color.
2011/7/22 Lluís Batlle i Rossell
> Maybe my opinion is of little value, but I like what fossil is currently
> doing
> with branches and colors. I use it since months and I'm very happy with it,
> not
> needing anything more.
>
>
Basically everything Fossil's added since early 2008 has been "extra
On Fri, Jul 22, 2011 at 03:14:38PM -0400, Richard Hipp wrote:
> On Fri, Jul 22, 2011 at 3:07 PM, Ross Berteig wrote:
>
> >
> > It would be nice if branches had a default color distinct from
> > the trunk. ... One way to do that that *might* be ... generate a hash of
> > the branch tag
> > name an
On Fri, Jul 22, 2011 at 3:07 PM, Ross Berteig wrote:
>
> It would be nice if branches had a default color distinct from
> the trunk. ... One way to do that that *might* be ... generate a hash of
> the branch tag
> name and use it for the color.
>
Do you have a suggested hash algorithm that will
At 05:54 AM 7/22/2011, Remigiusz Modrzejewski wrote:
>On Jul 22, 2011, at 14:46 , Richard Hipp wrote:
>> The --bgcolor on the last commit is optional. But it is nice
>> to have color on branches.
>
>By the way: this is one of the more cumbersome things about the
>UI. I'd really like to see t
Hello,
I am a fossil newcomer trying to see if it can fit our selfhosted-SCM
dreams.
I noticed that actually fossil does not support ipv6 (it is using
AF_INET socket)
Yet I was able to reach my fossil repo from an ipv6 adress inspiried
by :
http://www.sqlite.org/debug1/tktview?name=b0894abc94
Th
On Fri, Jul 22, 2011 at 9:50 AM, Stephan Beal wrote:
> On Fri, Jul 22, 2011 at 2:54 PM, Remigiusz Modrzejewski
> wrote:
>>
>> By the way: this is one of the more cumbersome things about the UI. I'd
>> really like to see this done automatically. But then again, I don't feel
>> like wasting my time
On Fri, Jul 22, 2011 at 9:55 AM, Rene wrote:
> Fossil thinks my configure script is binary. This probably due
> to one or more chars like ^H or something like that.
>
> Is there a way to convince fossil that it is not binary?
> And I don't want to change the configure script!
>
More likely, this
On Jul 22, 2011, at 15:50 , Stephan Beal wrote:
> On Fri, Jul 22, 2011 at 2:54 PM, Remigiusz Modrzejewski
> wrote:
>
>> By the way: this is one of the more cumbersome things about the UI. I'd
>> really like to see this done automatically. But then again, I don't feel
>> like wasting my time on t
Fossil thinks my configure script is binary. This probably due
to one or more chars like ^H or something like that.
Is there a way to convince fossil that it is not binary?
And I don't want to change the configure script!
--
Rene
___
fossil-users maili
On Fri, Jul 22, 2011 at 2:54 PM, Remigiusz Modrzejewski
wrote:
> By the way: this is one of the more cumbersome things about the UI. I'd
> really like to see this done automatically. But then again, I don't feel
> like wasting my time on this, so I don't expect anyone to waste theirs...
>
The pro
On Jul 22, 2011, at 14:46 , Richard Hipp wrote:
>fossil commit --branch autosetup --bgcolor '#91d680'
>
> The --bgcolor on the last commit is optional. But it is nice to have color
> on branches. If you forget it, it can be added later using the Edit feature
> of the UI. (That's how I add
On Jul 22, 2011, at 13:57 , Steve Bennett wrote:
> So I created the 'autosetup' branch and added a commit which drh then merged
> to trunk.
>
> Is that branch now defunct?
If your changes are well integrated into trunk, and you're not continuing
development in isolation from trunk, you should
On Fri, Jul 22, 2011 at 7:57 AM, Steve Bennett wrote:
> So I created the 'autosetup' branch and added a commit which drh then
> merged to trunk.
>
> Is that branch now defunct? If I want to propose some more, related
> changes,
> do I create a new branch, say autosetup2, or do I continue or resurr
On 22 Jul 2011, at 13:09, Lluís Batlle i Rossell wrote:
> On Fri, Jul 22, 2011 at 12:36:33PM +0100, Ben Summers wrote:
>>
>> On 22 Jul 2011, at 12:03, Lluís Batlle i Rossell wrote:
>>
>>> On Sun, Jul 10, 2011 at 01:03:06PM -0400, Martin Gagnon wrote:
Le 2011-07-10 à 11:05, Ben Summers a é
On Fri, Jul 22, 2011 at 12:36:33PM +0100, Ben Summers wrote:
>
> On 22 Jul 2011, at 12:03, Lluís Batlle i Rossell wrote:
>
> > On Sun, Jul 10, 2011 at 01:03:06PM -0400, Martin Gagnon wrote:
> >> Le 2011-07-10 à 11:05, Ben Summers a écrit :
> >>> Answering the question about breaking existing scr
So I created the 'autosetup' branch and added a commit which drh then merged to
trunk.
Is that branch now defunct? If I want to propose some more, related changes,
do I create a new branch, say autosetup2, or do I continue or resurrect the
autosetup branch?
If so, how?
Thanks,
Steve
--
µWeb:
On 22 Jul 2011, at 12:03, Lluís Batlle i Rossell wrote:
> On Sun, Jul 10, 2011 at 01:03:06PM -0400, Martin Gagnon wrote:
>> Le 2011-07-10 à 11:05, Ben Summers a écrit :
>>> Answering the question about breaking existing scripts, the output is
>>> identical when used at the root. Unless you're r
On Sun, Jul 10, 2011 at 01:03:06PM -0400, Martin Gagnon wrote:
> Le 2011-07-10 à 11:05, Ben Summers a écrit :
> > Answering the question about breaking existing scripts, the output is
> > identical when used at the root. Unless you're running scripts in a
> > sub-directory, nothing needs to chan
27 matches
Mail list logo
