On Sat 11 Aug 2018 11:47 AM, Andy Bradford wrote:
> Thus said "Andy Bradford" on 11 Aug 2018 11:41:01 -0600:
>
> > This is just a test.
>
> Only now at the end do I realize that Fossil Users allowed subscribers
> to hide their subscriber email address... pity.
>
Just curious, how did you masq
On Thu 02 Aug 2018 6:03 PM, joerg van den hoff wrote:
>
> the specific _concern_ here is the contemplated shutdown of this mailing
> list and mandatory(!) migration of all questions/discussions to the
> planned/upcoming fossil-scm forum. if that's what going to happen: so be it.
> but I would pref
On Thu 02 Aug 2018 11:02 AM, joerg van den hoff wrote:
> On 02.08.18 10:38, Steve Landers wrote:> On 31 Jul 2018, 9:47 PM +0800,
> Richard Hipp , wrote:
> >> I am about ready to merge the forum-v2 branch into trunk. If there
> >> are any objections, voice them quickly.
> >
>
> I could easily envisi
Hi All,
I'd like to know if there's a way to re-sync to the skin of a remote repo, but I
don't know of an option to do so.
If I cloned the sqlite3 repo from long ago, when I run fossil server, I'll see
the former skin. `fossil sync` doesn't seem to care about changes to the skin.
Is the skin som
On Fri 13 Jul 2018 4:22 PM, David Mason wrote:
> So I guess this is what Warren had in mind. Posting this in case it helps
> somebody on the list.
>
Taking this offtopic a little bit more...let's talk about VPNs.
Don't use PPTP and don't get tangled up in ipsec configuration hell.
Be happy wi
On Fri 13 Jul 2018 5:08 AM, Artur Shepilko wrote:
> > openBSD -current x64
> > $ cc -v
> > OpenBSD clang version 6.0.0 (tags/RELEASE_600/final) (based on LLVM 6.0.0)
> > Target: amd64-unknown-openbsd6.3
> > Thread model: posix
> > InstalledDir: /usr/bin
> >
>
> Ok, I think I found the problem. Th
On Thu 12 Jul 2018 5:47 PM, Richard Hipp wrote:
> On 7/12/18, Jungle Boogie wrote:
> >
> > Any clues?
>
> Could you tell us what platform you are trying to compile on?
Yes, sorry about that.
openBSD -current x64
$ cc -v
OpenBSD clang version 6.0.0 (tags/RELEASE_600/
Hi All,
Since commit 9c38803597 I can't build fossil successfully:
.obld/linenoise.o bld/shell.o bld/th.o bld/th_lang.o bld/th_tcl.o
bld/cson_amalgamation.o -lfuse -lm -lssl -lcrypto -lz -ldl
/usr/bin/ld: cannot find -ldl
cc: error: linker command failed with exit code 1 (use -v to see in
On Thu 12 Jul 2018 1:40 PM, Andy Bradford wrote:
> Thus said mario on Mon, 09 Jul 2018 18:06:52 +0200:
>
> > Our current homepage is a bit wall of textish / too bland I'd think.
> > While it already gets all interesting features across, it's not likely
> > enticing to new users.
>
> Here's a G
HI Mario,
On 9 July 2018 at 09:06, mario wrote:
> As followup to last month` Show time.. discussion:
>
> → http://fossilslideshow.tmp.include-once.org/
>
> (Take in mind this ain't a mockup yet; just as example.)
>
I think it's a good first step. Thanks for your efforts!
The carousal might be a
On 12:42AM, Wed, Jul 4, 2018 Nicola wrote:
>
> On 04/07/2018 00:18, Warren Young wrote:> On Jul 3, 2018, at 3:09 PM,
> Dewey Hylton wrote:
>
> >> I then attempted to change that latest commit by adding a 'trunk'
> tag and cancelling the new branch tag.
> >
> > Ow!
> As a newbie Fossil user, af
On 2 July 2018 at 09:05, Brian Nguyen wrote:
>> $ fossil clone https://www2.sqlite.org/docsrc doc.sqlite
>> Round-trips: 2 Artifacts sent: 0 received: 0
>> Error: not authorized to clone
>> Round-trips: 2 Artifacts sent: 0 received: 0
>> Clone done, sent: 537 received: 582 ip: 2.0.1.187
>>
Hi All,
I don't know if this has been reported already, but I'm getting a core dump when
running `fossil http` anywhere but within the fossil repo.
#0 sqlite3FindFunction (db=0x0, zName=0x6364d2e0220 "constant_time_cmp",
nArg=2, enc=1 '\001', createFlag=0 '\0') at ./src/sqlite3.c:31156
#1 0x000
Hi All,
Please see attached patch for your consideration. I found some text for the
various settings that could be updated.
Thanks!
Index: src/db.c
==
--- src/db.c
+++ src/db.c
@@ -15,11 +15,11 @@
**
***
On 28 June 2018 at 12:07, Richard Hipp wrote:
> On 6/28/18, jungle Boogie wrote:
>>
>> Does this help?
>> http://man.openbsd.org/man3/getrrsetbyname.3
>>
>
> That seems to be an OpenBSD-only library function. So, no, it doesn't
> really help.
>
On 28 June 2018 at 11:42, Richard Hipp wrote:
> On 6/28/18, jungle Boogie wrote:
>> Hi All,
>>
>> I know it's still very early on to make use of the new smtp logic, but
>> I thought I'd report these issues. Is anyone else experiencing issues
>> wi
Hi All,
I know it's still very early on to make use of the new smtp logic, but
I thought I'd report these issues. Is anyone else experiencing issues
with compiling?
FIG_H -D_HAVE_SQLITE_CONFIG_H -g -O2 -o bld/smtp.o -c bld/smtp_.c
./src/smtp.c:54:3: error: use of undeclared identifier 'ns_msg'
Hi All,
I spotted one small type in the email.c file:
Index: src/email.c
==
--- src/email.c
+++ src/email.c
@@ -2028,11 +2028,11 @@
/*
** WEBPAGE: announce
**
** A web-form, available to users with the "Send-Announcement" or "A"
On 25 June 2018 at 14:51, Richard Hipp wrote:
> On 6/25/18, jungle Boogie wrote:
>> If I inadvertently forward my email along
>> to someone/group without modifying the footer, the person/group would
>> be able to alter my subscription.
>
> How can I fix that?
>
I d
On 23 June 2018 at 13:07, Richard Hipp wrote:
> Just FYI:
>
> I have opened up email notifications on the canonical Fossil
> repository. To subscribe, visit:
>
> https://fossil-scm.org/fossil/subscribe
>
> Your help in finding creative ways of breaking the new system is appreciated.
>
This i
On Sat 23 Jun 2018 4:07 PM, Richard Hipp wrote:
> Just FYI:
>
> I have opened up email notifications on the canonical Fossil
> repository. To subscribe, visit:
>
> https://fossil-scm.org/fossil/subscribe
>
> Your help in finding creative ways of breaking the new system is appreciated.
Not
On Sat 23 Jun 2018 11:26 PM, Svyatoslav Mishyn wrote:
> (Sat, 23 Jun 23:03) Svyatoslav Mishyn:
> > quick typos:
>
> another one (+ previous one):
>
> -generated once the email notification systems stablizes.
> +generated once the email notification systems stabilizes.
>
> and
>
> - of the
On Sat 23 Jun 2018 4:07 PM, Richard Hipp wrote:
> Just FYI:
>
> I have opened up email notifications on the canonical Fossil
> repository. To subscribe, visit:
>
> https://fossil-scm.org/fossil/subscribe
>
> Your help in finding creative ways of breaking the new system is appreciated.
>
Hi All,
I think I've brought my repo up to trunk, did a little configuring of the email
page and attempted to add a subscriber, but I have a database error:
SQLITE_ERROR: no such table: subscriber
Database Error
no such table: subscriber SELECT 1 FROM subscriber WHERE suname='jungle'
--
On 22 June 2018 at 11:18, Richard Hipp wrote:
> Shown below is what I have at the moment. It is more succinct than
> other examples I've seen, but you can easily follow the link for
> details.
Very nice! I think you're on the right track!
___
fossil-u
On 22 June 2018 at 07:09, jungle Boogie wrote:
> On 22 June 2018 at 06:09, Richard Hipp wrote:
>> You may have noticed that I've been working on adding support for
>> email notifications or alerts to events on a Fossil repository. But I
>> need your help.
>>
&g
On 22 June 2018 at 06:09, Richard Hipp wrote:
> You may have noticed that I've been working on adding support for
> email notifications or alerts to events on a Fossil repository. But I
> need your help.
>
> When an event occurs (such as a check-in, or wiki-page edit) and a
> user wants a notific
On Thu 21 Jun 2018 7:47 PM, E Cruz wrote:
> On 06/21/2018 05:06 PM, Warren Young wrote:
>
> As mentioned in the original post, the majority of the time taken by the
> clone operation seems to be spent re-calculating the delta encoding of the
> large table definition files. I do not mind much th
All very, very lovely thinking! I just have one comment/question...
On 15 June 2018 at 10:35, Richard Hipp wrote:
> On 6/15/18, David Mason wrote:
>> I heartily agree with this... A flag to allow a person (including
>> Anonymous) to make a commit that would automatically go into a new branch
>>
On 14 June 2018 at 13:30, Thomas wrote:
> Web forums are much more superior than mailing lists, in any possible
> direction.
>
Ah, yes, superior.
https://xkcd.com/979/
At this rate, I suggest we start using reddit more, it's at least more
diverse than a single stand alone forum.
https://www.redd
On 14 June 2018 at 08:58, Richard Hipp wrote:
>
> So there you have it: If you want to harass someone by sending them
> thousands of subscription confirmations, there is now a website to
> assist you. Do we need any further evidence that the heart of man is
> deceitful above all things, and des
On 13 June 2018 at 08:11, Warren Young wrote:
> On Jun 13, 2018, at 8:05 AM, Richard Hipp wrote:
>>
>> My current tthinking is to use a hybrid approach where subscribers get
>> emails just like ordinary mailing lists, but posting and replying is
>> via web-form only.
>
> If you do this atop Fossi
Hi Andy,
Seeing that you have a Gmail account, you could upload to Google drive and
make public. Then provide the link via email to that file.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailma
On Sun 03 Jun 2018 9:28 PM, Richard Hipp wrote:
> There is suddenly a big uptick in traffic to fossil-scm.org,
> apparently due to the recent GitHub rumor. Unlike that traditional
> "slashdot effect", though, the referrals seem to be coming for a large
> variety of sources.
>
> So, if anybody se
On Sun 03 Jun 2018 11:06 PM, Richard Hipp wrote:
> On 6/3/18, Jungle Boogie wrote:
> > On Sun 03 Jun 2018 10:47 PM, Richard Hipp wrote:
> >> On 6/3/18, jungle Boogie wrote:
> >> >
> >> > Since it's linked from the homepage, maybe this can be update
On Sun 03 Jun 2018 10:47 PM, Richard Hipp wrote:
> On 6/3/18, jungle Boogie wrote:
> >
> > Since it's linked from the homepage, maybe this can be updated to show that
> > a) project website is still updated and b) to show fossil is still
> > efficient.
> >
&g
On Sun 03 Jun 2018 9:28 PM, Richard Hipp wrote:
> There is suddenly a big uptick in traffic to fossil-scm.org,
> apparently due to the recent GitHub rumor. Unlike that traditional
> "slashdot effect", though, the referrals seem to be coming for a large
> variety of sources.
>
> So, if anybody se
On 6:28PM, Sun, Jun 3, 2018 Richard Hipp wrote:
>
> There is suddenly a big uptick in traffic to fossil-scm.org,
> apparently due to the recent GitHub rumor. Unlike that traditional
> "slashdot effect", though, the referrals seem to be coming for a large
> variety of sources.
>
> So, if anybody s
Thus said Warren Young on Sat, 28 Apr 2018 20:24:16 -0600
On Apr 28, 2018, at 1:07 PM, Richard Hipp wrote:
(1) The new days=N query parameter shows all activity within the
previous N days.
Nice!
I think this will end up being more useful than “max N any type,” as I
frequently find myself f
On Sat 14 Apr 2018 6:22 AM, Richard Hipp wrote:
> Article: https://sqlite.org/whynotgit.html
>
> HN discussion: https://news.ycombinator.com/item?id=16806114
>
> Reddit discussion:
> https://www.reddit.com/r/programming/comments/8c2niw/why_sqlite_does_not_use_git/
>
Really good article with l
Thus said Richard Hipp on Sat, 7 Apr 2018 16:12:43 -0400
To get the latest trunk check-in, do this:
https://whatever.dom/fossil/tarball/trunk/download.tar.gz
That's awesome! Thanks for pointing this out and the link to the document!
___
fossil-
Hi DRH,
I think this commit is real useful:
https://www.fossil-scm.org/index.html/info/3e94c7ed74a07741
Thanks!
To enhance it a little more, what do you think about having the latest
commit on trunk having a generic filename such as trunk.zip/.tar.gz/.sqlar?
In this event, you wouldn't need
On 26 March 2018 at 12:27, Scott Doctor wrote:
>
> A while back I created a new repository for a project I ressurected. Checked
> it after creating with the fossil ui that all files included and such.
> Everything OK.
>
> My project contains many folders and a couple hundred files for a multi
> pr
On 2 February 2018 at 07:08, Warren Young wrote:
> On Sep 16, 2017, at 12:57 PM, John Found wrote:
>>
>> On Sat, 16 Sep 2017 13:44:51 -0500
>> Andy Goth wrote:
>>
>>> Please type "openssl version" and let us know what it prints.
>>
>> OpenSSL 1.1.0f 25 May 2017
>
> There’s a known bug in that v
On 21 December 2017 at 07:34, jungle Boogie wrote:
> On 20 December 2017 at 13:13, jungle Boogie wrote:
>> Hi All,
>>
>> I know a tech note entry in the timeline can be linked to a specific commit.
>> For example:
>> http://fossil-scm.org/index.html/timeline?ss
On 24 January 2018 at 13:45, Warren Young wrote:
> On Jan 24, 2018, at 1:47 PM, Warren Young wrote:
>>
>> On Sep 16, 2017, at 1:27 PM, Andy Goth wrote:
>>>
>>> Indeed, 1.1.0f is a version which includes the BIO_ADDR type, which is a
>>> union containing struct sockaddr_in6 among others. I don't
Hi All,
For your consideration...
Index: src/skins.c
==
--- src/skins.c
+++ src/skins.c
@@ -39,23 +39,23 @@
static struct BuiltinSkin {
const char *zDesc;/* Description of this skin */
const char *zLabel; /* The directo
On 8 January 2018 at 04:27, Richard Hipp wrote:
> On 1/8/18, Antoine Chavasse wrote:
>> I'm not sure I can fix this from the skin, since the background color for
>> ticket reports are configured by the user in the settings.
>>
>
> I might need to enhance Fossil to recognize this situation and mak
On 9 January 2018 at 06:32, Richard Hipp wrote:
> A new version of Fossil is now on trunk.
> (https://www.fossil-scm.org/fossil/info/9a33a240a2101ede) Please try
> again to build on every platform you have at hand, but especially all
> variations of MSVC and MinGW, and let me know whether or not
On 28 December 2017 at 12:02, Richard Hipp wrote:
> On 12/28/17, jungle Boogie wrote:
>> Hi All,
>>
>> I cannot clone a fossil repo running on a reaspberry pi.
>> --fossil-debug was originally used but since then, multiple fossil
>> binaries have been built w
>
> Any pointers are appreciated.
>
>
I created a brand new repo with zero commits and I was able to clone
it with fossil server running. So it looks like an issue with the repo
itself, perhaps enabling fossil debug on the binary caused an issue?
>
> --
> ---
> inum: 883510009027723
> sip: j
Hi All,
I cannot clone a fossil repo running on a reaspberry pi.
--fossil-debug was originally used but since then, multiple fossil
binaries have been built with it disabled.
>fossil clone http://10.7.0.82:8080 cpp_projects.f
Round-trips: 1 Artifacts sent: 0 received: 0
server replies with HTM
On Thu 21 Dec 2017 11:46 AM, Dominique Devienne wrote:
>
> Nice tip.
>
> Since I've seen DRH ask about available features on GitHub since I started
> lurking on this list recently,
> I'd mention the graphs the latter provide which I find useful, in the
> Insights tab of a project.
> The Code Freq
On Fri 22 Dec 2017 6:13 AM, Warren Young wrote:
> On Dec 21, 2017, at 4:57 PM, jungle Boogie wrote:
> >
> > On 21 December 2017 at 15:03, Warren Young wrote:
> >> On Dec 21, 2017, at 2:58 PM, jungle Boogie wrote:
> >>> perhaps left of the username.
>
On 21 December 2017 at 15:03, Warren Young wrote:
> On Dec 21, 2017, at 2:58 PM, jungle Boogie wrote:
>>
>> 3) Small green lock, like you see in your browser for https
>> 2) Unlocked & red
>> 1) Locked, but grey
>
> That’s going to make the red-green
On 21 December 2017 at 14:16, Richard Hipp wrote:
> On 12/21/17, jungle Boogie wrote:
>>
>> How are the signatures verified?
>
> Signatures are not verified, at the moment.
>
> Probably each repository would have a set of trusted public keys.
> Then as each che
On 21 December 2017 at 13:46, Richard Hipp wrote:
> Suppose Fossil were enhanced to show an icon beside each check-in that
> indicated whether or not the check-in had been signed and whether the
> signature had been verified. Thus, there are three states: (1)
> unsigned, (2) signed but unverifie
On 20 December 2017 at 13:13, jungle Boogie wrote:
> Hi All,
>
> I know a tech note entry in the timeline can be linked to a specific commit.
> For example:
> http://fossil-scm.org/index.html/timeline?ss=m&n=200&y=e&advm=0
>
> See the top commit by AG.
>
> C
Hi All,
I know a tech note entry in the timeline can be linked to a specific commit.
For example:
http://fossil-scm.org/index.html/timeline?ss=m&n=200&y=e&advm=0
See the top commit by AG.
Can a commit message contain the [ID] of a tech note and have it linked to it?
Otherwise, how do you list a
On 19 December 2017 at 13:59, Florian Balmer wrote:
> No, my patches were about intercepting the enter key from text input
> elements to submit the form and update the view.
>
> In my tests, I found that the "onchange" handler worked fine for
> drop-down lists, so you may have detected a new probl
On 19 December 2017 at 13:16, Florian Balmer wrote:
> As the form has no "submit" element, it works differently in different
> web browsers. I've sent a set of patches directly to Richard Hipp to
> make use of the "onkeydown" ("onkeyup" in the initial version) instead
> of the "onchange" handler f
Hi All,
When I change from Check-ins to tech notes on my personal repo,
there's not an automatic display of the results. I have to enter into
something like the "max" box and press enter to change the tech notes.
I noticed on the fossil-scm repo, there's some update to the page and
it displays the
Thus said Richard Kipp on Sun, 17 Dec 2017 21:11:30 -0500
You can now see the canonical Fossil self-hosting repository using any
of the built-in skins by visiting links from this page:
https://www.fossil-scm.org/skins/
Thanks for the link, this is a very handy way to see all the skins.
This is
Thus said Warren Young on Mon, 18 Dec 2017 17:55:16 -0700
I want to restrict this thread to the technical issues: preventing
wyoung/tangent confusions, or helping Donny trust Alice, or or giving Donny the
tools to *not* trust Alice just because Bob trusts Alice.
I can't remember the repo drh
On 14 December 2017 at 10:07, Richard Hipp wrote:
> On 12/14/17, jungle Boogie wrote:
>> Hi All,
>>
>> This commit caught my eye:
>> http://fossil-scm.org/index.html/info/ec059849f5c73a43
>>
>> User & Date:wyoung on 2017-12-13 21:37:20
>> Or
Hi All,
This commit caught my eye:
http://fossil-scm.org/index.html/info/ec059849f5c73a43
User & Date:wyoung on 2017-12-13 21:37:20
Original User & Date:tangent on 2017-12-13 21:37:20
So Warren edited a file at the same exact time as tangent?
Clicking on tangent, I see this:
http://fossil-scm.o
On 13 December 2017 at 07:58, Warren Young wrote:
> I’d feel differently if Fossil owned the directories, but it doesn’t.
> They’re mine; leave them alone!
Yes, I agree. I think this topic has been raised here in the past,
although that was about removing files. Still, If I created the
directo
On 13 December 2017 at 11:08, Richard Hipp wrote:
> On 12/13/17, jungle Boogie wrote:
>> On 13 December 2017 at 09:07, Warren Young wrote:
>>> On Dec 13, 2017, at 9:55 AM, Richard Hipp wrote:
>>>>
>>>> Would Git or GitHub have told me about those pr
On 13 December 2017 at 09:07, Warren Young wrote:
> On Dec 13, 2017, at 9:55 AM, Richard Hipp wrote:
>>
>> Would Git or GitHub have told me about those prior tickets?
>
> GitHub is pretty good about surfacing such information, as long as the ticket
> references the checkin ID.
Yep. With most pr
On 6 December 2017 at 11:22, Richard Hipp wrote:
> There have been lots of changes (hopefully, "improvements") to the web
> interface of Fossil over the past few days. If you have not be
> following the developments, I encourage you to visit a few of the main
> sites running the latest code and l
On 30 November 2017 at 10:55, Warren Young wrote:
> On Nov 30, 2017, at 8:16 AM, jungle Boogie wrote:
>>
>>mkcss.exe ..\src\default_css.txt default_css.h
>> ..\src\default_css.txt:1: syntax error
>
> Has src/default_css.txt changed? Try reverting it.
>
Th
On 30 November 2017 at 08:07, Marc Simpson wrote:
> Re: CSS issues: I think the default skin would be a bit more readable
> with 1 or 2 pixels of space between these newly added commit
> bubbles/boxes.
>
> (Adjacency currently yields a doubly thick shared line.)
Comparing to the sqlite skin, I ag
On 30 November 2017 at 08:43, Richard Hipp wrote:
> On 11/30/17, jungle Boogie wrote:
>> On 30 November 2017 at 07:46, Richard Hipp wrote:
>>> On 11/30/17, jungle Boogie wrote:
>>>>
>>>> Still failing with latest changes and nmake /f Makefile.msc and w
On 30 November 2017 at 07:46, Richard Hipp wrote:
> On 11/30/17, jungle Boogie wrote:
>>
>> Still failing with latest changes and nmake /f Makefile.msc and with
>> buildmsvc.bat:
>>
>
> Sorry you are having trouble. It works for me. Please suggest a fix..
On 30 November 2017 at 06:36, Martin Gagnon wrote:
> Do ctrl-f5 to force a full refresh. CSS is cached.
>
Yes, now it back!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-
On 29 November 2017 at 15:35, jungle Boogie wrote:
> On 29 November 2017 at 15:06, jungle Boogie wrote:
>> Hi All,
>>
>> First time to compile Fossil on Windows in awhile, so this might me a
>> fault of my own doing.
>>
>> ..\src\../skins/original/h
On Nov 30, 2017 3:35 AM, "Richard Hipp" wrote:
>
> On 11/30/17, jungle Boogie wrote:
> >>
> >> In previous builds, this commit would certainly have a number of green
> >> lines, but that's not the case anymore.
> >
> > bisect complete
On Nov 29, 2017 9:29 PM, "Jungle Boogie" wrote:
>
> Hi All,
>
> I don't think this is just an issue with my browser...
>
> https://www.fossil-scm.org/index.html/info/c94f6085489effe6
>
> In previous builds, this commit would certainly have a number of
Hi All,
I don't think this is just an issue with my browser...
https://www.fossil-scm.org/index.html/info/c94f6085489effe6
In previous builds, this commit would certainly have a number of green
lines, but that's not the case anymore.
Same with the unified diff version, too:
https://www.fossil-s
On Sat 25 Nov 2017 9:17 AM, Richard Hipp wrote:
> The SQLite project is mirrored on GitHub (not by me). This mirror
> provides a good opportunity to compare the interfaces of GitHub and
> Fossil using the same underlying data.
>
> https://sqlite.org/srcx/timeline?basic
> https://github.c
On 29 November 2017 at 15:06, jungle Boogie wrote:
> Hi All,
>
> First time to compile Fossil on Windows in awhile, so this might me a
> fault of my own doing.
>
> ..\src\../skins/original/header.txt
> ..\src\../skins/plain_gray/css.txt ..\src\../skins/plain_gr
> ../ski
On 29 November 2017 at 15:06, jungle Boogie wrote:
> Hi All,
>
> First time to compile Fossil on Windows in awhile, so this might me a
> fault of my own doing.
I'm using Microsoft Visual Studio 2017, by the way.
___
fossil-users ma
Hi All,
First time to compile Fossil on Windows in awhile, so this might me a
fault of my own doing.
..\src\../skins/original/header.txt
..\src\../skins/plain_gray/css.txt ..\src\../skins/plain_gr
../skins/plain_gray/header.txt ..\src\../skins/rounded1/css.txt
..\src\../skins/rounded1/details
On Tue 28 Nov 2017 10:36 PM, Andy Bradford wrote:
> Thus said Richard Hipp on Mon, 27 Nov 2017 17:41:55 -0500:
>
> > I have installed the new look (temporarily at least) on
> > https://www.fossil-scm.org/fossil so that we can live with it for a
> > while to see how we like it.
>
On Tue 28 Nov 2017 10:40 PM, Andy Bradford wrote:
> Thus said Richard Hipp on Mon, 27 Nov 2017 17:41:55 -0500:
>
> > The big down-side is that less information is visible on a single
> > screen now, so you have to scroll more. But that seems to be the trend
> > with websites these days
>
On Sat 25 Nov 2017 9:17 AM, Richard Hipp wrote:
> The SQLite project is mirrored on GitHub (not by me). This mirror
> provides a good opportunity to compare the interfaces of GitHub and
> Fossil using the same underlying data.
>
> https://sqlite.org/srcx/timeline?basic
> https://github.c
On 27 November 2017 at 14:13, Warren Young wrote:
> On Nov 24, 2017, at 7:35 AM, Richard Hipp wrote:
>>
>> Which is better?
>>
>> A: https://www.fossil-scm.org/a/timeline
>> B: https://www.fossil-scm.org/b/timeline
>
> I prefer A because I don’t like having to dig for details. Hiding details
On Sat 25 Nov 2017 6:46 PM, Zakero wrote:
> To help make the ellipses more visible, you could put them in their own
> and let the skin figure out what looks best. Also, instead of
> using "...", what about "[+]"?
>
Yes, I support this suggestion. Most sites I've seen that can expand/shrink
in
On Fri 24 Nov 2017 7:25 PM, sky5w...@gmail.com wrote:
> Wow, #5 is super clean and easy on the eyes!
> And #12 is interesting if I can see it with Per-Item Time Format = (off)?
>
> Thanks for the changes!
#5 is nice, and especially with the easy option to switch back to
advanced. Perhaps the bas
Hello All,
I think I've noticed this 'problem' before but I don't know what I did
about it. It's really just a minor annoyance and not a bug.
$ fossil version
This is fossil version 2.4 [bf69c6enc9] 2017-11-04 14:56:23 UTC
But that hash is from this commit, which is post 2.4 release:
http://
On 31 October 2017 at 17:18, Jacob MacDonald wrote:
> That is indeed the issue. There are command line flags to get Code to behave
> the way you want, but I don't recall them off the top of my head. Try
> searching for how to use Code as Git's editor, and use the same command as
> Fossil's editor
Good call, Stephan.
Thanks for the input, Jacob. I'll take a look for the arguments to use.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Hi All,
I would like this to be my editor on Windows:
"C:\Program Files\Microsoft VS Code\Code.exe"
I was able to set it up as my editor:
>fossil set editor
editor (local) "C:\Program Files\Microsoft VS Code\Code.exe"
I wanted to commit a change:
>fossil ci
This opened VS Code an
On 14 September 2017 at 09:12, Johan Kuuse wrote:
> On Thu, Sep 14, 2017 at 5:55 PM, Richard Hipp wrote:
>> If you'd like to help promote Fossil to unwashed masses who are still
>> using Git, perhaps like or retweet
>> https://twitter.com/robmurrer/status/908080904781869056 :-)
>
> Working in a 1
On 20 August 2017 at 10:24, Andy Goth wrote:
> On 08/18/17 07:38, Dewey Hylton wrote:
>>
>> I predict this to be the best email I receive today.
>>
>> My first thought was "This is like paid support!"
>> My second thought was "Wait ... paid support has *never* been this good
>> ..."
>>
>> Thanks f
On 15 July 2017 at 03:58, Johan Kuuse wrote:
> On Fri, Jul 14, 2017 at 9:23 PM, Venkat Iyer wrote:
>> Consider me old fashioned, but the current behavior seems more in line with
>> traditional unix (read sysv) commands.
>
> I don't want to make this a big deal, but I don't agree that the
> comma
On 14 July 2017 at 08:21, Richard Hipp wrote:
> On 7/14/17, jungle Boogie wrote:
>>
>> The command to edit commits after they've been commited is amend:
>> https://www.fossil-scm.org/index.html/help?cmd=amend
>>
>> example:
>> fosisl amend abc123
On 14 July 2017 at 03:21, Richard Hipp wrote:
> On 7/14/17, Olivier R. wrote:
>> So what is the recipe to move a check-in to another branch?
>
> I (the original author of Fossil) always use web-based UI for this.
> First run "fossil ui" to get the web interface going. Then find the
> check-in yo
On 6 June 2017 at 06:50, Johan Kuuse wrote:
> Hi,
>
> The following commands, executed without any arguments, are mute:
>
> f add
> f rm
> f delete
> f forget
>
> IMHO, they should show a help message instead.
>
Is it desired to not do anything with the command isn't followed by a
filename/argume
On 10 July 2017 at 16:56, Richard Hipp wrote:
> On 7/10/17, jungle Boogie wrote:
>> Hi All,
>>
>> One very minor update to browse.c to add a comma:
>
> I don't think that comma is correct. The most important comma rule I
> was taught in 8th grade was "
1 - 100 of 400 matches
Mail list logo