Re: [fossil-users] clone a repository over ssh where the path includes whitespace characters

Thus said Stephan Beal on Thu, 08 Aug 2019 12:06:30 +0200: > fossil clone 'ssh://user@domain://path/to/"directory with > spaces"/my.fossil' my.fossil Yes, that works, but it's a hack really because the user has to know that Fossil is using /bin/sh instead of simply calling exec() with

Re: [fossil-users] Fossil update

Thus said Zolt?n K?csi on Wed, 07 Nov 2018 20:48:11 +1100: > 'fossil update' (autosync/push/pull enabled) updates the local tree > but not to the latest version. This sounds like a cluster synchronization bug that was squashed after Fossil 1.29 was released:

Re: [fossil-users] Test From masquerading

Thus said Jungle Boogie on Sun, 12 Aug 2018 00:39:53 -0700: > Just curious, how did you masquerade your address? It might still work > on other mailing lists you're subscribed to. I have a script which sits as a wrapper around the /usr/sbin/sendmail interface that takes care of it all for me.

Re: [fossil-users] This mailing list is now deprecated

Thus said Warren Young on Fri, 10 Aug 2018 08:34:24 -0600: > > http://sqlite.1065341.n5.nabble.com/Problems-with-v3-9-0-entry-point-sqlite3-finalize-could-not-be-located-td85005.html#a85069 > > You only need to read the first post, not the whole thread. > > Fossil forums prevent that

Re: [fossil-users] Test From masquerading

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. Andy -- TAI64 timestamp: 400

[fossil-users] Test From masquerading

Hello, This is just a test. Andy -- TAI64 timestamp: 40005b6f1fd2 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] This mailing list is now deprecated

Thus said sky5w...@gmail.com on Fri, 10 Aug 2018 13:35:15 -0400: > Whoa, I still receive spam from this mail list. :( Correction: You received spam from spammers. The mailing list has yet to deliver spam as far as I can tell. I believe what you mean is that your email address that you use on

Re: [fossil-users] This mailing list is now deprecated

Thus said Warren Young on Wed, 08 Aug 2018 11:45:09 -0600: > > Will this ever be enabled? I prefer email over web forum posting. > > How would you prevent spammers from using an email submission > mechanism? Most mailing list managers prevent this by only allowing subscribers to submit

Re: [fossil-users] This mailing list is now deprecated

Thus said Richard Hipp on Wed, 08 Aug 2018 08:40:37 -0400: > New submissions via email are disallowed as an anti-spam > measure. Will this ever be enabled? I prefer email over web forum posting. Also, would it be a good idea to subscribe some of the mail archiving addresses for continuity?

Re: [fossil-users] The backoffice. Was: strange delay and messages during `fossil (uv) sync'

Thus said Richard Hipp on Tue, 07 Aug 2018 11:02:03 -0400: > That would delay the second HTTP request coming over the SSH connection. When I suggested that, I didn't understand enough about the backoffice design---specifically that it was a long-running task. After reading the forum page you

Re: [fossil-users] The backoffice. Was: strange delay and messages during `fossil (uv) sync'

Thus said Richard Hipp on Tue, 07 Aug 2018 10:21:34 -0400: > yes, we do want backoffice to run for SSH transport. Then I suggest that we simply make backoffice_run() smart enough to know that it has already run once: For example, perhaps instead of a panic here, backoffice_run() should just

Re: [fossil-users] The backoffice. Was: strange delay and messages during `fossil (uv) sync'

Thus said joerg van den hoff on Tue, 07 Aug 2018 16:10:15 +0200: > why did I see the problem only when actually cloning from another > machine, whereas a clone using ssh while being loggedin to the server > machine still worked? in both cases the ssh communication should be > the same,

Re: [fossil-users] The backoffice. Was: strange delay and messages during `fossil (uv) sync'

Thus said Richard Hipp on Tue, 07 Aug 2018 09:53:35 -0400: > Please build the from the tip of the forum-v2 branch and let me know > whether or not it is working for you. I was just about to submit a similar fix but you beat me to it. The reason why this doesn't work the same as a

Re: [fossil-users] Feature slideshow on fossil homepage

Thus said Jungle Boogie on Thu, 12 Jul 2018 13:54:04 -0700: > > http://fossil.bradfords.org/fossilthings.gif > > > > Does this look more enticing? > > That doesn't appear to establish a connection. Is your server down? The server was up, so is the firewall. :-) Try this instead:

Re: [fossil-users] Feature slideshow on fossil homepage

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 GIF animation of what it looks like in my browser:

Re: [fossil-users] Mailing list shutting down...

Thus said Richard Hipp on Wed, 13 Jun 2018 07:28:02 -0400: > The most recent problem is that robots are visiting the subscription > page and entering innocent user's email addresses and names. What about simply disabling web-based subscriptions and require people to subscribe via email?

[fossil-users] Bug in /finfo not showing Deleted anymore.

Hello, I haven't had the time to investigate further, but it seems that with this commit, the /finfo timeline no longer shows when a file gets Deleted: http://www.fossil-scm.org/index.html/info/4c268999d5 Thanks, Andy -- TAI64 timestamp: 40005b212f3a

Re: [fossil-users] How to rename a directory

Thus said Dingyuan Wang on Sun, 06 May 2018 00:37:23 +0800: > The fossil mv command seems can't rename a directory. I thought Fossil only tracked files (which is their complete path relative to the repository checkout) and does not actually track directories by themselves. For

Re: [fossil-users] Detecting checkout/repo mismatch

Thus said Richard Hipp on Thu, 29 Mar 2018 06:51:45 -0400: > You can't. But in more than a decade of use, this has never come up > before? Is this really a serious problem? Do we need to add new checks > to verify that the _FOSSIL_ file refers to the correct repository? I would say it's a

Re: [fossil-users] Any way to cleanup global _fossil or .fossil?

Thus said The Tick on Mon, 19 Mar 2018 15:43:07 -0500: > That did not seem to do much (if anything). There are still records > for repositories that no longer exist. What specific things in the .fossil file are you looking to have removed? fossil all ls seemed to clean up old

Re: [fossil-users] Experimental timeline "View Mode" changes.

Thus said Richard Hipp on Sat, 17 Mar 2018 12:02:41 -0400: > A new "Classic" viewing mode has been added to the timeline. I had a look at the test run sites... I prefer using the "Classic" view and also I think it makes sense to call it "Classic" as long as it retains the classic

Re: [fossil-users] Setting up an internet Fossil server

Thus said Scott Doctor on Sat, 24 Feb 2018 10:57:58 -0800: > I am having trouble getting fossil to work. What specifically are you having trouble with? Thanks, Andy -- TAI64 timestamp: 40005a91c739 ___ fossil-users mailing list

Re: [fossil-users] Why is i...@papier.host4free.ovh spamming the list?

Thus said Richard Hipp on Sat, 06 Jan 2018 17:06:31 -0500: > Either way, they have been permanently banished from the list, as of > about this time last night. You shouldn't be getting any new message > from i...@papier.host4free.ovh. Oh, I didn't realize it had already been squashed.

[fossil-users] Why is i...@papier.host4free.ovh spamming the list?

Hello, i...@papier.host4free.ovh has sent roughly 98 emails to this mailing list with nothing but ``Hallöchen!'' as the text (and a signature form an iPhone). The Subject in each is a variation of the original from Matt Welland, but often seems to have just a few characters altered,

Re: [fossil-users] fossil help set no longer provides essential information

Thus said Richard Hipp on Fri, 05 Jan 2018 13:42:29 -0500: > Maybe I just need to improve the "fossil help setting" output to > provide some clue about how to get help on individual settings? That would be an improvement as just in responding to this email I had to figure out how to get

Re: [fossil-users] fossil-users Digest, Vol 120, Issue 2

Thus said Stephan Beal on Tue, 02 Jan 2018 04:33:56 +0100: > That's not what i'm seeing: > > [stephan@host:~]$ echo -e "1\n2\n3" > 1 > 2 > 3 > [stephan@host:~]$ echo $(echo -e "1\n2\n3") > 1 2 3 Hmm, that's interesting. Have a look at this... Here's a file that has newlines in it, and which

Re: [fossil-users] fossil-users Digest, Vol 120, Issue 2

Thus said Stephan Beal on Tue, 02 Jan 2018 03:07:20 +0100: > That will still strip any newlines from his input, though, because > that's how $(...) works. It actually only strips the trailing newline. Any newlines in the middle of the file are fine. So for example: $ cat third.txt Third

Re: [fossil-users] How to cleanup two leafs on private branch?

Thus said Olivier Mascia on Mon, 01 Jan 2018 22:33:19 +0100: > WARNING: multiple open leaf check-ins on private: > (1) 2018-01-01 17:21:25 [cf17bd1315] (current) > (2) 2017-12-31 12:49:25 [6e96981da8] > There is really nothing wrong. I just would like to 'close' those > leafs or the

Re: [fossil-users] ticket length limitation

Thus said Sergey Bronnikov on Mon, 01 Jan 2018 12:44:42 +: > $ echo "fossil ticket add title "title" comment \"$(cat content)\"" | wc -c > 469207 > > Is there any workaround? There is one workaround that I'm aware of. If you chop your comment up into chunks you could do something like:

Re: [fossil-users] id of a ticket added via command line

Thus said Sergey Bronnikov on Sun, 31 Dec 2017 11:40:48 +: > For import purpose I use 'fossil tickets' commands, like this: fossil > ticket title "title" comment "comment" and it creates new ticket in > Fossil SCM. After this I need to add other messages as comments. But > how to

Re: [fossil-users] fossil server on a small private LAN

Thus said Warren Young on Thu, 28 Dec 2017 08:20:21 -0700: > I'm pretty sure I've never seen Fossil crash in the years I've been > running it. I've had it dump core a few times but those were generally due to bugs that were quickly fixed. Andy -- TAI64 timestamp: 40005a4540f3

Re: [fossil-users] Digital signatures on check-ins. Was: tangent vs. wyoung on recent commti

Thus said Richard Hipp on Thu, 21 Dec 2017 16:46:05 -0500: > 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. Regarding such an enhancement, would it involve configuring

Re: [fossil-users] fossil --repolist showing no repositories

Thus said "dewey.hyl...@gmail.com" on Thu, 21 Dec 2017 13:40:36 -0500: > * fossil does serve both a repo file and a directory if these files > are copied to a different local directory. Unless things have changed, it is generally not recommended to run Fossil on a non-local filesystem.

Re: [fossil-users] fossil --repolist showing no repositories

Thus said Dewey Hylton on Wed, 20 Dec 2017 20:23:23 -0500: > All users have read/write permissions on those files, so this doesn't > make sense (to me) from a Unix permissions standpoint. As Warren asked, what are the permissions on the directory that contains the Fossils? Not only does

Re: [fossil-users] fossil --repolist showing no repositories

Thus said Warren Young on Wed, 20 Dec 2017 21:02:01 -0700: > Linux containers aren't foolproof when it comes to permission > isolation. Better to not let Fossil have root privs even inside a > container. Fossil does chroot first and then drop root privileges which then

Re: [fossil-users] Timeline comments ignore all newlines AGAIN...

Thus said sky5w...@gmail.com on Mon, 18 Dec 2017 11:17:49 -0500: > I just compiled fossil version 2.5 [a6c5a4620a] 2017-12-18 02:06:40 > UTC under Windows 10 and nothing(every view option + CSS + Timeline > option) I try shows my commit comment[CR][LF]'s. What CSS and Timeline option are

Re: [fossil-users] Tag problems

Thus said David Mason on Sat, 16 Dec 2017 15:36:51 -0500: > I tried to add a tag to my fossil. After looking at the documentation > which said: The ``fossil tag'' command is for very low-level tag operations. You probably don't want to use it until you understand what it's doing. > 1) -n

Re: [fossil-users] tangent vs. wyoung on recent commti

Thus said Warren Young on Thu, 14 Dec 2017 12:13:18 -0700: > Fossil arguably has a bug here, where if you check a change in as > local user name ``tangent'', as I do here, then *later* do a ``fossil > sync'' to a URL with a user name, some bit of the local on-disk state > remembers that

Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

Thus said Warren Young on Mon, 11 Dec 2017 14:53:37 -0700: > To clarify the clarification, ``SHA256'' and ``SHA3-256'' are not the > same thing, though they are sometimes confused. And that is precisely why I called it a major correction. We're not even in the same family of SHA algorithms now.

Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

Thus said Richard Hipp on Sun, 10 Dec 2017 19:20:59 -0500: > Minor correction: the hash algorithm changes was from SHA1 to > SHA3-256. I would call that a major correction! I knew something didn't seem right about what I sent... Thanks, Andy -- TAI64 timestamp: 40005a2df05f

Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

Thus said Michai Ramakers on Sun, 10 Dec 2017 16:21:02 +0100: > michai@work-lap:/tmp/f/f$ f ver > This is fossil version 1.33 [b00e60194e] 2015-08-22 12:42:15 UTC Since then Fossil has had much development. In this case, the change that is breaking you is that the artifact IDs have

Re: [fossil-users] Forget large set of changes

Thus said Paolo Bolzoni on Mon, 04 Dec 2017 12:43:19 +0100: > The customer did an update and sent me the new version. This was > unexpected, as I from the discussion we had I understood that I was > pretty much the only one working on that. Fortunately, there were no > conflicts; but

Re: [fossil-users] Forget large set of changes

Thus said Paolo Bolzoni on Fri, 01 Dec 2017 09:18:10 +0100: > What happened is that I got an update of these files and the new > version changed the order of most the keys, but it changed only few > values. However, this changes in the order made the fossil diffs > confusing and

Re: [fossil-users] Forget large set of changes

Thus said Paolo Bolzoni on Thu, 30 Nov 2017 12:40:17 +0100: > It worked fairly well until I received an unexpected update of the > original files. I unpacked the new files in dir1 and fossil detected > hundreds of changes; looking better however this changes are mostly > just order

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Jungle Boogie on Tue, 28 Nov 2017 22:08:58 -0800: > In which mode? I think this is only an issue in the compact mode, > right? Yes, after further experimentation, the problem only exists with the Compact mode. Andy -- TAI64 timestamp: 40005a1fa5b8

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Richard Hipp on Tue, 28 Nov 2017 22:33:04 -0500: > Maybe "Verbose" should be modified to include the hash up front This was one of the factors that actually lead to my #1 ranking for Verbose. Andy -- TAI64 timestamp: 40005a1e5143

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Richard Hipp on Tue, 28 Nov 2017 22:08:38 -0500: > Please offer your opinions on: > > https://www.fossil-scm.org/b/timeline I see that you've corrected one of the problems I mentioned previously which was the melding of different comments in the same branch by introducing

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Richard Hipp on Mon, 27 Nov 2017 21:01:37 -0500: > As it was yesterday: >https://www.fossil-scm.org/fossil/timeline Hard to stomach (as previously mentioned). > Warren Young's new approach: >https://www2.fossil-scm.org/fossil/timeline Slightly better, but still has the

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Offray Vladimir Luna C?rdenas on Mon, 27 Nov 2017 18:20:44 -0500: > I agree with Warren's design and improved readability by adding space. > Timeline now has more "air to breath" and is more pleasant to the eye. If you're talking about what is currently visible on

Re: [fossil-users] A-B comparison of proposed timeline changes

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 There's another extremely annoying downside to this as

Re: [fossil-users] A-B comparison of proposed timeline changes

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. I tend to prefer having more information to less, but

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Jacob MacDonald on Fri, 24 Nov 2017 18:52:41 +: > Seems like I'm in the minority, but I prefer the A version. I tend to > like compact UIs and having all the relevant information close > together and the commit hash prominently displayed is nice. The only reason why I

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Richard Hipp on Fri, 24 Nov 2017 11:12:14 -0500: > Now fixed. Verified. > Other changes on https://www.fossil-scm.org/b/timeline since the > original comparison request: > > (1) The "details" section is shown on a separate line below the > check-in comment. I just

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Richard Hipp on Fri, 24 Nov 2017 10:13:22 -0500: > Alternative CSS that causes the "details" to appears on a separate > line from the comment: > > A: https://sqlite.org/src/timeline > B: https://sqlite.org/b/timeline I think it looks slightly cleaner with the ``details''

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Richard Hipp on Fri, 24 Nov 2017 09:35:55 -0500: > The change here is to emphasis the check-in comment and de-emphasize > the links to the check-in details and other information. Hopefully this change is simply accomplished with some CSS. That way those who prefer their UI to

Re: [fossil-users] A-B comparison of proposed timeline changes

Thus said Richard Hipp on Fri, 24 Nov 2017 09:35:55 -0500: > Which is better? > > A: https://www.fossil-scm.org/a/timeline > B: https://www.fossil-scm.org/b/timeline I prefer A. I don't like muted colors for text. I prefer seeing text than to have to look for text that begins to

Re: [fossil-users] Bug Report: Cloning with --private Fails

Thus said Martin Vahi on Wed, 01 Nov 2017 17:06:00 +0200: > Neither of the command lines prompted for the password of the user > martin_vahi, which is the admin username at the remote repository. You did not tell Fossil that there is a remote user associated with the repository. This

Re: [fossil-users] Bug Report: Cloning with --private Fails

Thus said Martin Vahi on Mon, 23 Oct 2017 11:27:03 +0300: > It doesn't even prompt for a password. You didn't give it a username for which it should prompt. Try: time nice -n18 fossil clone --unversioned --private --admin-user

Re: [fossil-users] web UI for a working checkout?

Thus said Steve Schow on Fri, 29 Sep 2017 15:43:38 -0600: > Who is hosting that and what is the longevity compared to github and > others? Longevity on the Internet seems to be an often nebulous thing. How long was Google Code (code.google.com) around? How long did Source Forge last before

Re: [fossil-users] Amended check-in time

Thus said Richard Hipp on Mon, 25 Sep 2017 16:04:32 -0400: > It does work sometimes, at least: https://fossil-scm.org/fossil/info/1f378f9e3 I've seen it work before too, so I'm not sure why it would be different with the steps Andy Goth provided. Guess it will take some

Re: [fossil-users] Amended check-in time

Thus said Andy Goth on Mon, 25 Sep 2017 10:45:23 -0500: > Has anyone tried running these commands yet? I want to see if anyone > else can replicate my problem. I just tried and was able to reproduce the problem. It happens on rebuild whether one does it via the ``fossil amend''

Re: [fossil-users] Amended check-in time

Thus said Andy Goth on Mon, 25 Sep 2017 10:45:23 -0500: > Has anyone tried running these commands yet? I want to see if anyone > else can replicate my problem. Sorry, I misinterpreted your comment about having a bad timezone (except in Narnia) as a retraction of your original problem. And now

Re: [fossil-users] Strange IP address on repository sync report.

Thus said Andy Bradford on Sat, 16 Sep 2017 11:09:18 -0600: > It might be useful here to also: > > print *p Of course, I meant *ip Andy -- TAI64 timestamp: 400059bd5b14 ___ fossil-users mailing list fossil-users@lists.fossil-scm

Re: [fossil-users] Strange IP address on repository sync report.

Thus said John Found on Sat, 16 Sep 2017 20:03:16 +0300: > Breakpoint 1, ssl_open (pUrlData=0x55a60c08 ) at > ./src/http_ssl.c:394 > 394 g.zIpAddr = mprintf("%d.%d.%d.%d", ip[0], ip[1], ip[2], ip[3]); > (gdb) p ip It might be useful here to also: print *p Andy -- TAI64

Re: [fossil-users] Strange IP address on repository sync report.

Thus said John Found on Fri, 15 Sep 2017 22:16:12 +0300: > I recompiled fossil from the latest trunk version, but without change. Did you run ``make clean'' before rebuilding? Thanks, Andy -- TAI64 timestamp: 400059bd5902 ___ fossil-users

Re: [fossil-users] Initial empty checkin?

Thus said Andy Goth on Wed, 16 Aug 2017 10:47:56 -0500: > What of this old thread? Are the issues it discusses still pertinent, > or have they been resolved? I believe all the relevant issues were actually resolved, however, I think it was still unfavorable given the time that was

Re: [fossil-users] Two easy questions

Thus said Steve Schow on Tue, 15 Aug 2017 15:50:39 -0600: > Thanks all for the helpful feedback, I will try to find a solution > outside of fossil. Whatever you end up doing, if possible please report back to the mailing list for the sake of the archive. That way if someone has the same

Re: [fossil-users] Using fossil across OSes

Thus said jerson on Thu, 27 Jul 2017 10:20:51 +0530: > I've not done anything special. The only commands I use are Can you show more detail about what you're doing? An exact transcript of the commands you're running followed by the errors you get would be much better. I tried your commands one

Re: [fossil-users] Fossil version 2.3 - 10th anniversary edition

Thus said Ross Berteig on Fri, 21 Jul 2017 11:13:47 -0700: > These are tests that failed, but were not expected to fail. They > should be investigated, especially as they did not fail in my builds. It looks like the output is different than what the test expects. For example, with

Re: [fossil-users] Fossil version 2.3 - 10th anniversary edition

Thus said Ross Berteig on Thu, 20 Jul 2017 11:35:39 -0700: > Well, I missed that target, but I did build and run the test suite > against the tip of trunk, [4872a58b] . > > The only failure was the test pre-commit-warnings-fossil-1. I tested against ae83b2137f and it looks alright I

Re: [fossil-users] Test message after IP address change

Thus said Richard Hipp on Wed, 12 Jul 2017 06:25:56 -0400: > There are reports that messages are not getting throught to this list > now. The current message is an attempt to reproduce the problem. This is a reply to verify. Andy -- TAI64 timestamp: 400059699f27

Re: [fossil-users] warning about unsaved changes with `fossil checkout --keep`

Thus said Natacha Port? on Fri, 07 Jul 2017 09:43:56 -: > (3) "fossil checkout --keep", which is advertised as changing the > "current commit" pointer without touching the working directory, but > bails out of there are unsaved changes. > (4) "fossil checkout --keep --froce", which changes

Re: [fossil-users] warning about unsaved changes with `fossil checkout --keep`

Thus said Natacha Port? on Thu, 06 Jul 2017 19:30:29 -: > Now imagine you leave things as they are after (3) to do some non-dev > stuff (or some dev on other repositories), and you receive a serious > windows-specific bug report. You drop everything to work on it, > forgetting the "fossil

Re: [fossil-users] Tech-note timeline commits

Thus said jungle boogie on Tue, 04 Jul 2017 15:03:01 -0700: > Now I greatly prefer the former, because when copying the hash with > the mouse, I can skip the closing (]) bracket, since I usually start > right-to-left. Not to derail your comments, but... Personally, I think that this is a

Re: [fossil-users] test-comment-format utf8

Thus said Stephan Beal on Thu, 15 Jun 2017 09:55:11 +0200: > Sidebar: i had no idea bash can do ranges like that! I usually use jot: $ echo $(jot -w '%c' 26 a) a b c d e f g h i j k l m n o p q r s t u v w x y z $ echo $(jot -w '%c' 26 a | sort -r) z y x w v u t s r q p o n m l k j i h g f e

Re: [fossil-users] Improvements to the /reports page

Thus said Roy Keene on Wed, 07 Jun 2017 10:45:27 -0500: > I would benefit from some improvements to the /reports page, such as > the ability to restrict the dates upon which are being reported and > the ability to restrict the report to certain tags. That sounds like it would be useful

Re: [fossil-users] Is it possible to merge repository's?

Thus said The Tick on Mon, 29 May 2017 22:35:31 -0500: > From this I gather that there would be no way to connect the imported > repository onto the main trunk. That was not what I was hoping for. You're correct, you would have 2 trunks. Andy -- TAI64 timestamp: 4000592dd034

Re: [fossil-users] Is it possible to merge repository's?

Thus said Stephan Beal on Tue, 30 May 2017 02:57:38 +0200: > However, there is _hypothetically_ a way to completely merge 2 repos > into one while keeping all commits, but i'm not at all certain if this > would work... I think it actually will work for some definition of ``work''. I've done it

Re: [fossil-users] [8c22e1bbcd8ec048] Regression: "fossil amend" no longer works unless operating from within an open checkout

Thus said fos...@rkeene.org on Thu, 25 May 2017 23:42:22 -0500: > Why is the check-out directory considered at all ? My guess is that it was an expedient fix to prevent a segfault. I agree with you that Fossil shouldn't care about whether or not the repository is open and just choose a

Re: [fossil-users] [8c22e1bbcd8ec048] Regression: "fossil amend" no longer works unless operating from within an open checkout

Thus said Roy Keene on Thu, 25 May 2017 21:17:15 -0500: > Given that this worked, why was it broken ? And can the error message > be converted to something that is actually coherent ? And can it be > unbroken ? Apparently it was broken intentionally because there was a segfault that happened

Re: [fossil-users] [8c22e1bbcd8ec048] Regression: "fossil amend" no longer works unless operating from within an open checkout

Thus said Roy Keene on Thu, 25 May 2017 21:26:50 -0500: > The fossil checkin I linked to ([8c22e1bbcd8ec048]) has the change in > src/info.c that enforces this for all cases. Yeah, I think you already said that and somehow I missed it. I wonder why this was introduced... Andy -- TAI64

Re: [fossil-users] [8c22e1bbcd8ec048] Regression: "fossil amend" no longer works unless operating from within an open checkout

Thus said Roy Keene on Thu, 25 May 2017 21:17:15 -0500: > Attempts to add tags to a repository using "-R" now returns an engrish > error message: The engrish error message has been addressed, however, it does look like somewhere the behavior has changed. I gave it a valid UUID and it still

Re: [fossil-users] [8c22e1bbcd8ec048] Regression: "fossil amend" no longer works unless operating from within an open checkout

Thus said Roy Keene on Thu, 25 May 2017 21:17:15 -0500: > $ fossil amend -R ~autobuild/aurae.fossil --tag build-pass --tag > tests-fail > the "amend" command only work from within an open check-out What particular checkin are you trying to amend here? Seems like the error really

Re: [fossil-users] Apparently a bug in ticketing

Thus said Doug Franklin on Wed, 24 May 2017 17:09:52 -0400: > Sorry, Andy, that was me not being clear. I should've put "user > comment" in quotation marks because I was talking about the field on > the form labeled "User Comment". It was three tickets created by one > user (there's

Re: [fossil-users] Apparently a bug in ticketing

Thus said Doug Franklin on Mon, 22 May 2017 18:32:00 -0400: > 11. Oops. I don't have three tickets. I have two tickets. The first > ticket is fine. The original second ticket seems to be gone (it's not > in the "All tickets" list), and the current second ticket has all of > the values of

Re: [fossil-users] Apparently a bug in ticketing

Thus said Doug Franklin on Mon, 22 May 2017 18:32:00 -0400: > 11. Oops. I don't have three tickets. I have two tickets. The first > ticket is fine. The original second ticket seems to be gone (it's not > in the "All tickets" list), and the current second ticket has all of > the values of

Re: [fossil-users] Bug Report or a Feature Request: Cope with Hosting Providers' Watchdogs

Thus said Martin Vahi on Tue, 16 May 2017 22:43:07 +0300: > Are there any "heart-beat" options available, wher a cron job might > call something like No, however, there are options to control how much Fossil will sync in a single round-trip. Fossil does synchronize individual artifacts

Re: [fossil-users] How to transfer/move/upload local repository to chiselapp.com

Thus said The Tick on Sun, 14 May 2017 17:19:21 -0500: > What is the status of chiselapp.com and is it a viable place to put an > open source repository as of 2017? As far as I know it is still viable. Andy -- TAI64 timestamp: 400059193379 ___

Re: [fossil-users] Problem with: fossil revert -r xxx

Thus said Ross Berteig on Wed, 10 May 2017 21:35:12 -0700: > But in my experience, fossil revert is a rarely used command. I use revert quite frequently to abandon changes I don't want anymore. I don't often use it with -r though. Andy -- TAI64 timestamp: 400059146dec

Re: [fossil-users] Limiting cruft in my repos

Thus said David Mason on Wed, 10 May 2017 01:07:22 -0400: > If the students were very disciplined, they would assiduously edit > ignore-glob to prevent this. But if there is one thing that students > (en-mass) are not, it's disciplined! Do students generate their own Fossil, or is the

Re: [fossil-users] Couple of beginner questions

Thus said The Tick on Thu, 30 Mar 2017 14:35:22 -0500: > Goodness! All I wanted was to have a comment contain a copyright > character. Did you see my response? You could have continued on the way you were doing things. No need to change anything except tell your browser that the

Re: [fossil-users] Couple of beginner questions

Thus said The Tick on Wed, 29 Mar 2017 15:47:32 -0500: > If I edit the file, of course the utf-8 copyright symbol is garbled. > Furthermore, there is no way I can insert a utf-8 character. My editor (nvi) allows me to insert UTF-8 characters by typing the ASCII character, then by pressing

Re: [fossil-users] Couple of beginner questions

Thus said Warren Young on Wed, 29 Mar 2017 14:25:34 -0600: > Any text editor or compiler that can't cope with UTF-8 in 2017 is > broken or can be ignored. I rarely use any editor but nvi. It doesn't support UTF-8. Here is what utf16le.txt (from Fossil test directory) looks like to me:

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

Thus said Warren Young on Mon, 27 Mar 2017 10:21:42 -0600: > Explain to me how someone deciding between Fossil and Git gets down to > automatic pagination as the key differentiator, the one that seals > their decision. While it may not be used as a determining factor in deciding between Git

Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager

Thus said Roy Keene on Thu, 23 Mar 2017 17:36:37 -0500: > I vote that the pagination be off by default to preserve the existing > behaviour -- terminals have been able to scroll for decades now so I > don't know why systemd/git like to do this by default but it is REALLY > annoying having to

Re: [fossil-users] Crash with this AMEND command

Thus said "Tony Papadimitriou" on Sat, 18 Mar 2017 01:59:21 +0200: > The following command crashes fossil (older and up to current > version). It doesn't crash for me. Can you be more specific as to which version? Also, which OS? Thanks, Andy -- TAI64 timestamp: 400058ce1e81

Re: [fossil-users] The SHA3 transition as firewall

Thus said Warren Young on Thu, 09 Mar 2017 13:37:35 -0700: > On Mar 9, 2017, at 1:03 PM, Richard Hipp wrote: > > > > If a new artifact Y' which has the same SHA1 hash as Y comes along, > > it will be discarded, since an artifact with that same hash is > > already in the

Re: [fossil-users] spam after posting to the list

Thus said Richard Hipp on Sun, 05 Mar 2017 11:33:57 -0500: > I got rid of the spam from Eboni by blocking the following IP addresses: > > 144.217.94.196 > 144.217.165.151 > 2607:5300:201:3000::/64 Thanks. I checked my block list and apparently those are not on it. But I don't

Re: [fossil-users] Longest gap between check-ins

Thus said Rolf Ade on Wed, 22 Feb 2017 00:16:40 +0100: > SELECT count(*) FROM event > WHERE type = 'ci'; > > returns 10324. But after a > > fossil ui > > http://localhost:8080/timeline?n=11000=ci > > shows only 10285 check-ins. Try: http://localhost:8080/timeline?n=11000=ci And also:

Re: [fossil-users] Longest gap between check-ins

Thus said Richard Hipp on Mon, 20 Feb 2017 10:39:09 -0500: > Now remind me again, how would you do this in Git? ;-) To get these kinds of reports I import my Git repositories into Fossil. :-) Andy -- TAI64 timestamp: 400058ab1b40 ___

  1   2   3   4   5   6   7   8   9   10   >