Re: [fossil-users] Last call for "testerCleanup" branch review...

Can someone shed some light (or point me to a link) as to what this new feature is supposed to do? (I must have missed any prior discussion on this.) -Original Message- From: Joe Mistachkin Sent: Saturday, March 05, 2016 9:27 PM To: fossil-...@mailinglists.sqlite.org Cc: 'Fossil SCM

Re: [fossil-users] Shorter alias for FOSSIL AMEND --EDIT-COMMENT request

Seems OK to me. -Original Message- From: Ross Berteig Sent: Friday, February 26, 2016 4:57 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Shorter alias for FOSSIL AMEND --EDIT-COMMENT request On 2/25/2016 4:58 PM, to...@acm.org wrote: Would it be possible to

[fossil-users] Shorter alias for FOSSIL AMEND --EDIT-COMMENT request

Would it be possible to add a short version for the –-EDIT-COMMENT option of the AMEND command (just like there is for –-comment)? Something like –e perhaps? --EDIT-COMMENT is the one option I use most often when using the AMEND command to fix check-in comment typos, and this option is a bit

Re: [fossil-users] Two questions

1. How do you merge only certain files? The way I deal with the problem you described is with the UPDATE command. FOSSIL UPDATE BRANCH FILENAME will merge only that specific file. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

[fossil-users] Suggestion for MERGE default comment

When merging one branch to another, the merge usually reflects more than a single commit. So, just like when a commit is aborted, the next time you try to commit you’re given the previously typed comment as default, it would be nice if after merging, the default comment for the next COMMIT

Re: [fossil-users] Suggestion for MERGE default comment

From: Stephan Beal Sent: Sunday, January 17, 2016 3:11 AM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Suggestion for MERGE default comment On Sun, Jan 17, 2016 at 1:53 AM, wrote: important. This is less work than trying to (remember and) type all details

[fossil-users] Display of *private* branches

Would it possible to have private branches display as such (e.g., marked as PRIVATE) both in the UI ‘Branches’ screen, and the FOSSIL BRA cli command? Thanks and Happy New Year!___ fossil-users mailing list fossil-users@lists.fossil-scm.org

[fossil-users] PUSH --PRIVATE failure (bug?)

Just reporting some probable bug. I created a private branch during commit (in one step) and then tried to push it (with F PUSH –PRIVATE) on the remote repo (which is a file on a USB stick), and got this error, and the push failed (I tried several times). The –db-check says OK on the

Re: [fossil-users] Fossil mentioned on HN

Hmm.. If one can create a private branch, do all draft work there and when done merge to trunk (or other non-private branch), then sync with the main repo, the main repo will not contain any traces of the private branch (with the draft work). Am I correct? So, if then the local repo is deleted

[fossil-users] BUNDLE problems/questions - resent to the correct list this time :)

1. I’m trying to create a new repo by taking a branch from an existing one. So, I thought the easier way would be the new ‘bundle’ feature. I tried this batch file (Win7): - f new xxx.fossil --date-override 2014-01-01 f o xxx.fossil f bun export xxx --standalone --branch %1 –R

[fossil-users] Suggestion for local/global settings enhancement

Certain settings, like ignore-glob or binary-glob can have a really long list of items, which may be edited from time to time. Ideally, the global setting should have the ones that apply to all repos, while the local setting only the ones that apply only to that specific repo. The problem is

Re: [fossil-users] Why does the repo file grow over time?

Funny thing is that for some repos, the file will shrink even further if you re-run the command a 2nd time. -Original Message- From: Richard Hipp Sent: Saturday, November 28, 2015 1:52 AM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Why does the repo file grow over

Re: [fossil-users] Unexpected merge conflict

But did you have to spoil our innocence? :) From: Stephan Beal Sent: Saturday, November 14, 2015 11:11 AM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Unexpected merge conflict On Sat, Nov 14, 2015 at 2:14 AM, wrote: f up ... f me ... while i also use

Re: [fossil-users] Unexpected merge conflict

Thanks for the detailed explanation. It makes perfect sense now. Certainly, a rather difficult task to get right algorithmically. Many thanks also to all previous respondents. From: Scott Robison Sent: Saturday, November 14, 2015 8:22 PM To: Fossil SCM user's discussion Subject: Re:

Re: [fossil-users] Unexpected merge conflict

I have to agree with your first four sentences. Your prove-it-to-yourself example, however, is quite different from my case where all changes happened in the same branch, and trunk was unaltered (with respect to the lines in question). Obviously, if the same line of code changes on both sides

Re: [fossil-users] Unexpected merge conflict

The following Windows batch file will reproduce the condition I’m talking about (f = fossil): f new sample.fossil f o sample.fossil echo Hello > hello.txt f add hello.txt f com -m Initial echo Hello, World > hello.txt f com --branch other -m "Added World!" echo Computer

Re: [fossil-users] symlinks (was Re: xkcd on git)

Although I certainly agree with your point (and don’t care about symlinks myself, BTW), I’m afraid it’s a bit too late to expect portability of repos between platforms (mainly, Linux and Windows) without prior care from the repo maintainers. Just the fact the Linux has case-sensitive

[fossil-users] fossil v1.34 unexpected CLEAN command changes from v1.33

I built the latest version and (unfortunately, for me) CLEAN no longer asks for confirmation. Is this something I can have behave the way it was in v1.33 via some setting? (I often do a clean but may want to skip some file, so I like to be asked.) If not possible anymore, is there at least

[fossil-users] Question about MERGE

Today I tried something and got an unexpected result. So, I would like to know what the right way would have been. I created a new branch and made a whole bunch of changes. Some of these changes were tested, and so I decided to merge them in to the trunk. I did this by going to trunk, and

Re: [fossil-users] Question about MERGE

OK, but doesn't cherry-pick work the same as a MERGE but only for single version of the timeline? My intent was to get all changes from the branch (the whole history) but for specific files, only. -Original Message- From: Richard Hipp Sent: Wednesday, October 28, 2015 6:00 PM To:

Re: [fossil-users] How to close an empty branch?

Very easy to reproduce (Win7, f = fossil): f new sample.fossil f o sample.fossil echo Hello > somefile f add somefile f com --branch ghost -m "Save in some branch" f tag cancel ghost af9e rem The actual ID above may differ f up ghost rem not found: ghost f bra f up --does

[fossil-users] How can I get 'Check-ins' by default in timeline (instead of Any Type)?

How can I get 'Check-ins' by default in timeline (instead of Any Type)? Thanks.___ 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] How to close an empty branch?

I ran into the same problem just yesterday. Took me a while to figure out a solution. (And, this may not be the only way but it worked well.) In my case there were two possibilities. For one, I could just do 'unhide' and see the related timeline. The other (like yours, probably) did not show

Re: [fossil-users] How to close an empty branch?

This makes wonder. Is there any practical reason to allow a check-in without any tags? If not, maybe a warning should be issued when trying to cancel the only remaining tag of a check-in. From: to...@acm.org Sent: Saturday, October 24, 2015 11:19 AM To: Fossil SCM user's discussion Subject:

Re: [fossil-users] MERGE problem (with renames/deletes)

I’ve been reading much of this discussion so far, and although it has focused primarily on the possibility of a deleted file not merging in as one may have expected, I have to say that my report was not about that. What I reported had to do with the addition of new files in trunk that were

[fossil-users] FOSSIL LS bug?

With this setting: relative-paths (local) 1 doing FOSSIL LS . from within a subdirectory displays the full path (from the root or the repo). I tried with older version and current trunk and get the same behavior. ___ fossil-users mailing list

Re: [fossil-users] diff after update

Although I think --undo is not too bad as it clearly does not make sense to 'undo' a diff, another alternative that is less 'verbal' that might work is diff --back (as in "diff with what would be there if I were to go back, or back out the recent changes...") -Original Message-

Re: [fossil-users] Automatically put version / checkout infomation into source code on commit

To get the checkout version into your app, one way (I've been using successfully) is this: With the help of a little script (like the following Lua one) extract the checkout version into a file that is included from your app. This file is generated as part of the make build process and is

[fossil-users] FOSSIL UPDATE behavior -- feature or bug?

Using the UPDATE command, when trying to bring in a subdirectory from another version (I tried both from a different branch and from the same branch and I get the same behavior), and that subdirectory does not exist in the current version, nothing happens saying “changes: None. Already

[fossil-users] WARNING: multiple open leaf check-ins on trunk:

I updated to this recent version of fossil: This is fossil version 1.33 [282ae5e4de] 2015-05-28 17:05:13 UTC Compiled on May 28 2015 21:56:18 using msc-18.00 (32-bit) SQLite 3.8.10.2 2015-05-20 18:17:19 2ef4f3a5b1 Schema version 2015-01-24 zlib 1.2.8, loaded 1.2.8 SSL (OpenSSL 1.0.2a 19 Mar 2015)

Re: [fossil-users] WARNING: multiple open leaf check-ins on trunk:

(BTW, this is a private repo). So, if this is a new feature, it means the problem was there all along and I simply now found out about it! Great! What I see at that time is the following (I hope the image won’t disappear – if it does, get it here:

Re: [fossil-users] Linux compilation problem (Ubuntu v14) and is rebuild needed?

OK, got it working with these 3 steps: make clean ./configure make Q2: Do I need a rebuild after going to v1.33 from v1.32? Regarding Q2 I meant is a FOSSIL REBUILD required when going from 1.32 to 1.33? Although it seems the database schema hasn't changed from fossil v1.32 (based on

[fossil-users] Linux compilation problem (Ubuntu v14) and is rebuild needed?

Q1: How do I solve this? (I have already tried ./configure and didn’t make any difference) ./bld/piechart.o: In function `piechart_render': ./src/piechart.c:176: undefined reference to `sincos' ./src/piechart.c:179: undefined reference to `sincos' ./src/piechart.c:191: undefined reference to

[fossil-users] Fossil [f4aed6661c] compilation problem MSVC

..\src\piechart.c(145) : error C2065: 'M_PI' : undeclared identifier ..\src\piechart.c(157) : error C2065: 'M_PI' : undeclared identifier___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Fossil [f4aed6661c] compilation problem MSVC

Yes, it now works. Thanks. BTW, if you're also interested in some long-standing warnings (with MSVC again), here they are: ..\src\url.c(459) : warning C4090: 'function' : different 'const' qualifiers ..\src\url.c(460) : warning C4090: 'function' : different 'const' qualifiers

[fossil-users] FOSSIL STASH wish list

To add to the perpetual wish list: Can the STASH [SAVE] command be made to behave similarly to the COMMIT command with respect to comments in the editor? That is, if nothing is typed as stash comments, the stash operation to be aborted. It currently does not allow one to abort, and if you

Re: [fossil-users] Branch only timeline

+1 (wish list) I don't think there is as I had asked for the same quite some time ago. But, I guess an option like -b [branch] could be added eventually to do this. (Similar to how -p can be used to filter by given file/dir name.) Example: -b without an explicit branch name to show timeline

Re: [fossil-users] Bug? FOSSIL MV does not work as expected (Win7machine)

I’m aware of the “within the repository”, and actually I’m not among those who are so interested in this changing this, as proposed by others. So, not the same issue here. What I’m reporting is unrelated to changes happening on disk. If you run the example below you should not be allowed to

[fossil-users] Can fossil be used to apply a diff patch?

Can fossil be used to apply a diff patch (such as that created by the diff command)?___ 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] Can fossil be used to apply a diff patch?

Thank you but I wanted this for a Win7 machine, not Linux. (I have MINGW installed but its 'patch' is a bit unstable as it crashes most of the time besides not being available on most Win7 machines.) That's why I was hoping fossil would be able to eat its own ... diff Bundle is not good when

Re: [fossil-users] Merge question

I think what you're looking for is to simply copy a file from one branch to another. The way I often do this is to use the update command to bring in those files (usually one or very few files) from whatever other branch (any check-in really -- even from same branch, older version). No need

Re: [fossil-users] Two trunks?

But, what if the two forks become incompatible when merged? For your proposed auto-merge to work, it’s enough that the two forks simply touch (alter) different files. An auto-merge would obviously work without producing conflicts as neither fork touches files touched by the other fork. Now,

Re: [fossil-users] Version 3.8.9 is in testing

Just in case this was not intentional. I have received this only from the Fossil list(s), but not SQLite's. BTW, the introduction of the .dbinfo shell command made the more commonly used .dump come later and now needing more than just .d to invoke it. Bummer :( -Original Message-

Re: [fossil-users] New timeline display options

+1 -Original Message- From: Andy Bradford Sent: Tuesday, March 31, 2015 7:20 PM To: Matt Welland Cc: Fossil SCM user's discussion Subject: Re: [fossil-users] New timeline display options Thus said Matt Welland on Mon, 30 Mar 2015 21:08:49 -0700: +1 circular nodes, +1 colored

[fossil-users] Minor bug that causes some confusion

This is on a Windows machine so, filenames are case insensitive. To reproduce (f = fossil): f new xxx.fossil f o xxx.fossil echo Hello hello f add hello f cha f ext f rev Hello f cha f ext Problem 1: “f rev Hello” does not revert the ADD (note: Hello is given with a different case from the

Re: [fossil-users] Select specific changes within files

++1 From: Scott Robison Sent: Friday, March 20, 2015 11:08 PM On Fri, Mar 20, 2015 at 2:55 PM, Steve Stefanovich s...@stef.rs wrote: If we are discussing partial, I'm more interested in partial checkouts than partial commits, i.e. having the ability to checkout a specific directory only.

Re: [fossil-users] Is this a crazy idea?

I was about to suggest the same because I often have this situation, also. I need to commit a large number of files, except one or two which are still no ready for commit. I’ve been thinking about what the simplest way from a user’s point of view would be, and I think if in the editor that

Re: [fossil-users] Timeline graph display options

Although both are good, my vote is for nomo=0 (choice 1) as being the one that 'goes to 11' :) -Original Message- On Mon, Mar 09, 2015 at 11:06:59PM -0400, Richard Hipp wrote: Which timeline graph do you prefer: (1) https://www.fossil-scm.org/fossil/timeline?y=cinomo=0 (2)

Re: [fossil-users] Justification for two-step mv and rm

You could always have a global setting on how to deal with this (old way vs new way) to keep everyone happy :) -Original Message- From: Richard Hipp Sent: Tuesday, March 03, 2015 11:22 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Justification for two-step mv and rm

[fossil-users] Fossil's reported app name under Windows firewall

I was trying to modify firewall settings for fossil to work as server under Windows 7, and (even after adding fossil.exe again and again) I couldn't find any program named fossil or even containing the word fossil in the list of firewall enabled apps. To make a long story short, after lots of

Re: [fossil-users] New search features

https://www.dropbox.com/s/vujnqzgx3iaiu64/fossil.exe?dl=0 From: Richard Boehme Sent: Tuesday, February 03, 2015 1:58 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] New search features Does anyone have a Windows binary of the latest fossil with search? I don't have the ability

[fossil-users] Windows 'make' broken?

I tried to compile the latest fossil with SSL, and failed with the following errors: cl -DOPENSSL_NO_SSL2 -DOPENSSL_NO_SSL3 /Fotmp32\cversion.obj -Iinc32 -I tmp32 /MT /Ox /O2 /Ob2 -DOPENSSL_THREADS -DDSO_WIN32 -W3 -Gs0 -GF -Gy -nologo - DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN

Re: [fossil-users] File age in the tree view

Just to note that on Win7 (Firefox browser – if it matters), the mouse-over shading is so faint that if I hadn’t read about it here I wouldn’t have noticed it at all. Can you make it a little more visible?___ fossil-users mailing list

Re: [fossil-users] How to force text for all files?

How about this idea? During 'commit' when asked file contains binary data. Use --no-warnings or the binary-glob setting to disable this warning. Commit anyhow (a=all/y/N)? to have one more option (Text) to override the automatic detection. Something like: file contains binary data. Use

Re: [fossil-users] How to force text for all files?

I'm not sure about the exact characters that may be causing this as each file has different ones. (What characters would make the file binary in fossil’s eyes?) I'm dropping a zip with two examples here (www.dropbox.com/s/bmjp65hfcv1ex9w/text_or_bin.zip?dl=0) that I happened to use lately,

Re: [fossil-users] How to force text for all files?

No irony at all. Certainly a file is either *assumed* to be text or binary, not both at the same time. But isn’t ‘binary’ (or ‘text’) a matter of perspective/interpretation? I don’t know of any formal definition or international standard of what constitutes ‘binary’ or ‘text’ files. For

Re: [fossil-users] How to force text for all files?

-Original Message- From: Will Parsons And how could one possibly distinguish a file containing all 256 byte bit patterns from a binary file? That's the point, in effect you can't. It's up to you to decide how to interpret a file. Referring to all 256 ASCII codes is a misnomer.

[fossil-users] How to force text for all files?

Hi, I’m looking for a way to force all files (except those matching binary-glob) to be treated as text rather than automatically (mis-)detected as binary. Any way to do that? TIA___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] How to force text for all files?

One common (for me) example is a text file that includes maybe just one or two special 8-bit ASCII codes. This causes the whole files to be stored as binary and makes it impossible to ‘diff’. From: Richard Hipp Sent: Saturday, December 06, 2014 10:16 PM To: Fossil SCM user's discussion

Re: [fossil-users] Possible bug: Failure to acknowledge changes after failing to overwrite write-protected file

And I have to ask: Why do you have to ask? :) A problem is a problem regardless of how it became evident. No, I don’t keep read-only files under fossil control, obviously. Note I used the word ‘happens’ to be read-only. The read-only status was set to temporarily protect this one file from

Re: [fossil-users] Possible bug: Failure to acknowledge changes after failing to overwrite write-protected file

I agree it’s not an everyday use case. I’ve been using fossil for nearly a year now, and it happened to me only once, just now. And, I’ve learned my lesson, so I’ll be more careful for this not to happen again. However, this is the kind of situation that it may not bite often at all but if

[fossil-users] Possible bug: Failure to acknowledge changes after failing to overwrite write-protected file

(This was seen on a Windows 7 machine) When opening a repo, if you select to overwrite all files, and a file to be updated happens to be read-only (R attrib set), the overwrite fails (it should) but if you then change the read-only to read-write, and try to see changes or try to revert the

Re: [fossil-users] Possible bug: Failure to acknowledge changesafter failing to overwrite write-protected file

From the F SET command I see blanks for either: mtime-changes ... repo-cksum Regarding mtime, I understand the batch file test maybe too fast for the time to change, but the problem was noticed on a file that was many hours away from the repo version. -Original Message- From: Kees

Re: [fossil-users] FOSSIL ALL

I tried it and it works very well. Thanks. So, I guess I can leave all repos open all the time at both locations, and only do PULL/SYNC/PUSH at start/end of work day. (I only worry a bit about the possibility of the USB eventually becoming full during a ‘push’ what consequences will it have

Re: [fossil-users] diff --tk features and to-dos. Was: Diff against working copy

Please save me the trouble of search - Do I have a Contributors Agreement for you in the firesafe? May I suggest this great SQLite3 tool to help you (1) keep track of your documents, and (2) quickly search for membership without even going to the safe? (Sorry, I couldn’t resist!

Re: [fossil-users] New TIMELINE with FILENAME option(WAS:FINFOsuggestion)

On Sun, Oct 19, 2014 at 10:14 AM, Stefan Bellon sbel...@sbellon.de wrote: But why not just use some switch to indicate that the following argument is a file/directory rather than a branch/tag/...? From: Stephan Beal +1: no ambiguity problem and no unconventional file prefix. So, I guess

Re: [fossil-users] New TIMELINE with FILENAME option(WAS:FINFOsuggestion)

On second thought, regarding these arguments (from Stephan Beal) : @ is conventionally used by some apps to mean include list from this file this is exactly what we need. Include the (timeline) list from this file (implying about this file) Plus, if we go with what some other apps do, then

Re: [fossil-users] New TIMELINE with FILENAME option (WAS: FINFOsuggestion)

Case sensitivity does not work for directory names, only for filenames. -Original Message- From: to...@acm.org Last change with case sensitivity for Windows works great. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] New TIMELINE with FILENAME option (WAS:FINFOsuggestion)

I re-ran all use cases I had tried before, and everything seems OK. * Case-insensitivity for Windows (OK) * Root directory (OK) * No duplicates (OK) From: Richard Hipp Sent: Saturday, October 18, 2014 1:36 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] New TIMELINE with

Re: [fossil-users] New TIMELINE with FILENAME option(WAS:FINFOsuggestion)

I don’t know if anyone has noticed already, but there is an inherent ambiguity between possible dirnames/filenames, and tag names or internal keywords, such as current now used by the timeline command. If there is a filename by the same name does the word refer to the filename, or to the

Re: [fossil-users] New TIMELINE with FILENAMEoption(WAS:FINFOsuggestion)

[3450ec3047] *CURRENT* Added now filename (user: tonyp tags: trunk) +++ no more data (1) +++ Thanks. From: Richard Hipp Sent: Saturday, October 18, 2014 10:09 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] New TIMELINE with FILENAMEoption(WAS:FINFOsuggestion) On Sat, Oct 18

Re: [fossil-users] New TIMELINE with FILENAME option (WAS: FINFOsuggestion)

That's because 'trunk' is incorrectly interpreted as filename. This is related to the same problem I have already reported about filenames having priority over internal keywords and tags, instead of the other way around. I suspect it will be fixed soon. -Original Message- From:

Re: [fossil-users] New TIMELINE with FILENAME option (WAS:FINFOsuggestion)

I see three possibly easy solutions: 1. An SQL SELECT on the tag and keyword list decides whether to treat a word that has no slash as keyword/tag (exists), or filename (not exists). If there is a slash it is always a filename. 2. A possibly faster executing way (without having to run SQL

Re: [fossil-users] FINFO suggestion

I guess the timeline equivalent would work, too! However, I'd be more interested in being able to see just the code changes (i.e., check-ins) and not all the 'noise' about wiki edits, tickets, tags, etc which the timeline gives by default (unless one uses the -t ci option). So, I thought

Re: [fossil-users] FINFO suggestion

I did a quick try, and it seems to work OK with only one small exception, the root directory itself (where _FOSSIL_ is). There, “fossil tim .” for example (which works OK in subdirectories), shows nothing “+++ no more data (0) +++” when obviously there is quite a lot because if I give “fossil

Re: [fossil-users] FINFO suggestion

One more problem I see is that it sometimes shows the same timeline entry multiple times in a row (same SHA1 and description) From: to...@acm.org Sent: Friday, October 17, 2014 7:51 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] FINFO suggestion I did a quick try, and it

Re: [fossil-users] FINFO suggestion

An observation related to the last problem. The identical multiple entries seem to match the number of files that have changed in that subdirectory. So, if three files changed, the same timeline entry appears three times. From: to...@acm.org Sent: Friday, October 17, 2014 8:30 PM To: Fossil

Re: [fossil-users] New TIMELINE with FILENAME option (WAS: FINFO suggestion)

Seems to work much better. I no longer get duplicates. Thanks. (I haven't yet checked whether the entries I see are the correct ones, e.g., no missing ones, but on first inspection the timeline seems correct). So, for now the only remaining problem I can see is the failure to show any

Re: [fossil-users] New TIMELINE with FILENAME option (WAS: FINFO suggestion)

This new timeline functionality really makes a huge difference in everyday work! Thank you all. -Original Message- From: Martin Gagnon On Fri, Oct 17, 2014 at 10:43:53PM +0300, to...@acm.org wrote: So, for now the only remaining problem I can see is the failure to show any changes

Re: [fossil-users] New TIMELINE with FILENAME option (WAS: FINFO suggestion)

Last change with case sensitivity for Windows works great. One note about the previous fix regarding the repo root. It assumes (based on comment in source) equivalence to no filename given. But this prints 'noise' like tickets, wiki edits, etc. So, I guess a simple fix is to force enable the

Re: [fossil-users] New TIMELINE with FILENAME option (WAS: FINFOsuggestion)

Again, thanks for the quick fix regarding forced -t ci on filename. Works perfectly. As far as I can tell this new feature is complete! Great work! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Ordering ticket priority/severity

I suppose the simplest solution would be to rename them to start with the required digit. Example: 1 Critical 2 Important -Original Message- From: org.fossil-scm.fossil-us...@io7m.com Sent: Monday, October 13, 2014 12:00 AM To: fossil-users@lists.fossil-scm.org Subject:

Re: [fossil-users] Is it possible to add empty folders to the repo?

(BETTER YET: Is it possible to REMOVE empty folders?) For me, there is an even more ‘annoying’ problem with the way empty directories are handled, but I think it is the opposite use case. For example: You have version X that has subdirectories a, b, and c. And, another version Y that has only

Re: [fossil-users] I have two trunks?

If it helps: I tried something very simple (in this example: https://chiselapp.com/user/rberteig/repository/WPCLI/home), and it apparently fixed the problem in cloned copy at least. I shunned the empty initial checking, rebuilt, and re-enabled the artifact (just in case). The timeline

Re: [fossil-users] How to use the ticket subsystem?

Thanks, this is great! One problem though! The values I set are not pulled to my local copy. Is that expected? (Server is Fossil version [3d49f04587] 2014-01-27 17:33:44 client is fossil version 1.30 [ee46563cbd] 2014-08-15 12:46:27 UTC) From: Stephan Beal Sent: Tuesday, September 30, 2014

Re: [fossil-users] Compilation with SSL option fails on Win7

I'm afraid several changes were made that were not directly related to the problem I was having at all, even if they may have added greater robustness to the build process. (BTW, I always did NMAKE from within the win subdirectory that contains the makefile.msc so that was definitely not part

[fossil-users] Compilation with SSL option fails on Win7

Here's what I do: (I have installed the latest perl - Strawberry Perl, and I have installed openssl-1.0.1i.tar.gz under the compat subdirectory) Then (with MSVC) I do: nmake -f Makefile.msc FOSSIL_ENABLE_SSL=1 and after some successful work, it halts with this message: --

Re: [fossil-users] Compilation with SSL option fails on Win7

Update (if it helps): The problem appears in the latest trunk version [e061a675e6]. I also tried with an earlier version [ee46563cbd], and it worked OK. But the latest trunk fails consistently, so something must have broken in between these two. -Original Message- From:

Re: [fossil-users] Compilation with SSL option fails on Win7

Nope! The same exact error. I uninstalled StraberryPerl before installing ActivePerl. So, the problem is elsewhere. Also, as I mentioned in the follow-up email: The problem appears in the latest trunk version [e061a675e6]. When I tried with an earlier version [ee46563cbd], it worked OK.

Re: [fossil-users] Compilation with SSL option fails on Win7

I'm building on Win7 64-bit. Tomorrow, at work, I can try again on a Win7 32-bit, and see if that makes a difference. Version [ee46563cbd] built without any errors, and apparently has SSL support (much larger file size, and an attempt to connect to an HTTPS server did not produce errors

Re: [fossil-users] gdiff/opendiff on os x: suppress unchanged files?

If it's any consolation, the same problem exists under Windows with WinDiff (default GDIFF program). I suppose the reason for this is the screening of which files to show is done by the application, and not fossil. And, WinDiff, in my case has no problem showing a comparison between two

Re: [fossil-users] gdiff/opendiff on os x: suppress unchanged files?

Here’s a very easy way to verify the problem (at least on a Win machine): (F = FOSSIL) (This is fossil version 1.30 [ee46563cbd] 2014-08-15 12:46:27 UTC) 1. f g --from prev any_unchanged_file_path 2. f diff --tk --from any_unchanged_file_path [1] will show the files but without any differences.

Re: [fossil-users] gdiff/opendiff on os x:suppress unchanged files? (OOPS)

Here’s a very easy way to verify the problem (at least on a Win machine): (F = FOSSIL) (This is fossil version 1.30 [ee46563cbd] 2014-08-15 12:46:27 UTC) 1. f g --from prev any_unchanged_file_path 2. f diff --tk –from prev any_unchanged_file_path [1] will show the files but without any

Re: [fossil-users] gdiff/opendiff on os x: suppress unchanged files?

There is a Show Identical Files option in WinDiff but changing only affects whether the contents of the files are shown, or a blank screen is shown. The problem is still that the WinDiff application is invoked even though there is no difference in the files. -Original Message- From:

Re: [fossil-users] gdiff/opendiff on os x: suppress unchanged files?

Wait a moment, did you specify a path/file with the GDIFF command, or was it a show-me-all case, i.e., no files given? Because the latter will correctly go only through the files that have changed. The problem appears when you specify a set of files (even a single one). Then, all specified

Re: [fossil-users] gdiff/opendiff on os x: suppress unchanged files?

MessageOK, but still you need to try with a file that has NOT changed. It should show nothing, but you will see the file, instead. From: dave Sent: Wednesday, September 24, 2014 11:17 PM To: 'Fossil SCM user's discussion' Subject: Re: [fossil-users] gdiff/opendiff on os x: suppress unchanged

[fossil-users] UI diff issue

Hi all, (This is fossil version 1.30 [ee46563cbd] 2014-08-15 12:46:27 UTC) When using the UI to look at differences between versions by marking the little square boxes to indicate the ‘from’ and ‘to’ versions, if you mark the ‘from’ but need to go a different page (using newer/older) to mark the

Re: [fossil-users] UI diff issue

Oh, I see. Well, one possible solution I can think without knowing if it would be easy (or even possible) to implement: When someone selects a ‘from’ box, the script should update the links for older/newer options to include the selected ‘from’ parameter. [Perhaps the URL (for Older/Newer)

Re: [fossil-users] UI diff issue

Correction: upon pressing (say, Older) should become something like: upon selecting a ‘from’ should become something like: From: to...@acm.org Sent: Sunday, September 21, 2014 3:45 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] UI diff issue Oh, I see. Well, one possible

Re: [fossil-users] diff with --from --to

I suppose you’re referring to this comment: “Note that --from branch --to current and --from branch are not quite the same thing. The second form (without the --to) does a diff between the branch and the code in the current check-out including local uncommitted changes. Adding the --to

  1   2   >