(Apologies if this message appears twice – I’m having some SMTP issues.)
I attempted to minimize storage by running “fossil reb --compress” on various
fossils. Only one result was unexpected.
Below is a copy of the db --db-check before and after a REBUILD with –-COMPRESS
option. The ‘after’ is
-Original Message-
From: Richard Hipp
Other ideas for what to name this (hypothetical and unimplemented) command:
fossil contribute
fossil bequest
fossil bestow
fossil proffer
Some more ideas (in random order):
fossil chip-in (shortest possible is ch)
fossil enqueue (shorte
1. I have some Wiki/MD files created from the web UI. Can I move them to the
source tree and still keep access to them from the web UI?
And the reverse.
2. I have some Wiki/MD files in the source tree (which I can see with the
http://repo/doc/version/filename.[md/wiki] link) but I cannot figur
I use WinMerge (http://winmerge.org/) which also let's you edit if you like.
Set as default with something like: fossil set gdiff-command
c:\WinMerge\WinMergeU.exe
There is also WinDiff (by MS) that doesn't let you edit, but it is an older
app and I'm not sure where I found it.
-Original M
-Original Message-
From: Warren Young
* The second is the presence of free pages not yet vacuumed. This is
unused space that IMO ‘unfairly’ lowers the ratio.
I disagree. The unused free pages *should* be charged against you, because
that is space Fossil is taking on your disk, and
It appears that the compression ratio shown with the ‘fossil db –db-check’
command is based on the actual total file size of the repo against the would-be
size of all expanded versions stored separately (based on description here:
https://www.fossil-scm.org/xfer/doc/trunk/www/stats.wiki).
There
The idea looks very good to me. But the ellipses are indeed barely visible.
How about replacing ... with [*] as a generic (foot)note mark?
-Original Message-
From: Richard Hipp
Timelines now come up in Basic mode, which means only the check-in
comment shows. There are ellipses at th
Seems OK now.
-Original Message-
From: Richard Hipp
Please rebuild using the latest trunk check-in and let me know if you
encounter any more problems.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.foss
Wiki tab and enter a dot in the search box and press the button.
It also happens with Ticket Search (and I didn't try the others) so I
suppose it's a common issue for all searches done this way.
-Original Message-
From: Richard Hipp
On 11/17/17, Tony Papadimitriou wrote
Just to report an issue I noticed today.
If I put just a dot [.] in the GUI Wiki/Search box and press ‘Search Wiki’ it
crashes.
This happens both with v1.37 that I normally use, and with version 2.4
[a0001dcf57] 2017-11-03 09:29:29 UTC
Thank you.___
A couple of questions about how unversioned files relate (or not) to normal
repo files.
1. When adding and then removing an unversioned file, does the file get
completely removed, or just the reference to it from the unversioned file list
is removed but the actual ‘blob’ remains? (If not autom
On Sep 7, 2017 18:43, "Tony Papadimitriou" wrote:
For example, assuming a checkout tree like this:
lib/file
a/b/c/d/e/f/g/h/j/file
and while inside the j subdirectory, I want to refer to lib/file by doing
something like:
fossil tim –p /lib/file
instead
For example, assuming a checkout tree like this:
lib/file
a/b/c/d/e/f/g/h/j/file
and while inside the j subdirectory, I want to refer to lib/file by doing
something like:
fossil tim –p /lib/file
instead of
fossil tim –p ../../../../../../../../lib/file
(and not sure if I got the number of .
When doing ‘annotate’ on a certain file version I see the most recent commit
responsible for each line in the file. That’s great!
However, if I want to know which previous commits (history) touched one
specific line, is there some way to do this?
Thanks.
___
In the UNVERSIONED export subcommand:
export FILE OUTPUT Write the content of FILE into OUTPUT on disk
would it be easy to make the OUTPUT filename optional so that if not present
the same name as FILE is assumed?
Thanks.
___
fossil-users mailing li
I use Wiki a lot for keeping short notes/memos about pretty much anything
related to the host repo.
For cosmetic purposes when viewing from a Web browser these notes often contain
... or other such formatting tags.
However, doing most programming from the command-line, when I want to quickly
I need a pre-compiled 32-bit Linux version of the release fossil
(The same Windows version says: This is fossil version 2.2 [81d7d3f43e]
2017-04-11 20:54:55 UTC)
The download page only offers a 64-bit Linux version.
(I’m locked out from being able to update either fossil or sqlite3 directly
fro
An alternate fix for [2d69772e] so that SEARCH without target behaves the same
both from within an open repo, and with the –R option.
if( g.argc<2 ) return;
blob_init(&pattern, g.argc<3?"":g.argv[2], -1);
___
fossil-users mailing list
fossil-users@lists
Hmm, I happen to use the REVERT command *all* the time. It's the simplest
(and possibly only direct) way I know to quickly abort all changes (after
experimenting with code) and go back to what was the check-in. How do the
rest of you do an abort?
I must admit I very rarely used the -r option
So, ignore ‘makefile’?
From: Ross Berteig
# ignore files without at least one dot somewhere in their name
!*.*
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
(Tested under Win7)
With FOSSIL SEA from within an open repository up to 1000 lines are printed by
default. Seems OK.
Now, if the same command is given with the –R option to the same repo (e.g.,
FOSSIL SEA –R repo.fossil) the results are different, and somewhat random.
If an empty string is ex
y from the command line so that I can redirect to a file.
Thank you.
-Original Message-
From: Richard Hipp
Sent: Monday, April 17, 2017 12:57 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Is there a way to find identical files?
On 4/17/17, Tony Papadimitriou wrote:
Is there a way to find identical files by the artifact ID?
So, if ID 123456... appears two or more times in the repo, I want to see all
the related paths.
(This could be either for a single check-in or the whole repo regardless of
check-in.)
Thanks._
Although not a critical issue, I think a dump should preserve the original
database’s page size (pragma page_size).
Some databases have been squeezed significantly by using some non-default value.
I feel this optimization should not be lost when restoring from a dump.
(I suppose there may be othe
The following command crashes fossil (older and up to current version).
fossil am trunk -R your_repo_here.fossil –e
(I thought the –R option was supported for this command, but regardless it
shouldn’t crash.)
___
fossil-users mailing list
fossil-users@
-Original Message-
From: Warren Young
(3) New repositories are initialized using SHA3
Maybe there should be a “fossil init --sha1” option for the technologically
conservative.
Or, for practical reasons. So, I second that.
For example, creating a new repo locally to be hosted by chi
-Original Message-
From: Warren Young
On Mar 1, 2017, at 2:03 AM, Tony Papadimitriou wrote:
My 'prediction' is that two versions will end up in a similar mess to the
Python 2.7 vs Python 3.x one.
[all irrelevant Python analysis removed]
I was referring to the fact that
My 'prediction' is that two versions will end up in a similar mess to the
Python 2.7 vs Python 3.x one.
Also, Fossil 2.0 will not be able able to get any significant updates due to
version collision with 2.1 (so, maybe 2.0 and 3.0 -- oops, more like
Python!)
And, having to remember which ver
-Original Message-
From: Warren Young
On Feb 26, 2017, at 6:34 PM, Tony Papadimitriou wrote:
how is it possible for someone to inject a 'bad' file with the same SHA1
as a 'good' file already in the repo?
Your attacker could be MITM’d into the sync stream. I gave a
Leaving aside for a moment the consequences in general of the presumed
imminent SHA1 collapse (and some of the valid points already made by Linus
regarding Git):
If FOSSIL will refuse (and I actually tried it with those two same SHA1
PDFs) to accept a file (commit, push, pull) with the same SH
Thank you for the tip, good to know.
(However, I think my point is still valid. Unless the repo visitor happens to
magically know about this /uvlist link there seems to be no obvious way to get
to it starting navigation from some main page.)
From: Martin Gagnon
To see the list of unversioned f
I placed some unversioned file to a chiselapp repo I maintain and then from the
Web UI tried to locate the file but without luck.
There isn’t even a hint that some unversioned file is in the repo, so that one
can try to UNV SYNC from the command line (after cloning).
Maybe the FILES tab should h
Hmm, but isn't it usually the newbies that do NOT read any documentation? :)
However, if this gets implemented here's a somewhat crazier thought to make
it ever better for the general public:
fossil set newbie-mode =
where is blank indicating "I don't know what I'm supposed to be doing
her
+1
This would also guard against unplanned/accidental use of same branch name
in a repo with tens of older inactive branches one cannot possible remember
at all times.
-Original Message-
From: Richard Hipp
Sent: Monday, February 06, 2017 6:18 PM
To: Fossil SCM user's discussion
Subj
Would it be possible for SEARCH to honor the –R option (just like TIMELINE
does) so that one can search without having to open the repo?
Thanks.___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mail
When I attempted to PULL with the command FOSSIL PULL –R FILE
but (by mistake of course) I pointed it instead to a PDF file, I got an endless
loop that ends with a crash. (Win7 machine.)
It happens with any recent version of FOSSIL I tried.
And it seems pretty much any PDF file will cause this be
I noticed that when a filter is applied to the timeline (such as ‘parent
current’), AND the –p option is used to filter for a specific file, then the –n
option (implicit or explicit) seems to count entries towards the limit
regardless of whether these are displayed or not. The result is you pre
The following steps should work assuming you haven't added any more commits
after the mistake (and haven't pushed your changes anywhere else). Also,
your current checkout is the one with the mistake (if not, first do F UP to
the appropriate check-in):
f co prev --keep
f pur ch tip
f com file1 fi
The following steps should work assuming you haven't added any more commits
after the mistake (and haven't pushed your changes anywhere else). Also,
your current checkout is the one with the mistake (if not, first do F UP to
the appropriate check-in):
f co prev --keep
f pur ch tip
f com file1
Just to report some unexpected problem that happened today.
After adding (ADD command) some files to trunk that where already part of a
different branch, and committing, I went to the other branch in question (with
UPDATE) and tried to MERGE trunk to include some other changes as well. Here’s
When doing STASH GO the check out is first updated to the baseline and then the
stash changes applied.
However, if a following UNDO is given, only the applied stash changes are
reverted. The baseline does not return to where it was before the STASH GO
command.
I don’t know if this is by desig
* For consistency, could you please add a DELETE alias to the REMOVE/RM
subcommand of the UNVERSIONED command? (I’m used to doing DEL and it’s
confusing to have to switch to REM for UNVERSIONED.)
* Would it be possible to also display the timestamp (real or –-mtime) of the
files when doing a
With the introduction of the new UNVERSIONED command, I thought there is no
longer need to keep certain binary images in the check-out as versioned files.
Instead, I want to keep only the latest version as unversioned files.
To remove all the versioned ones, is there is a simple way? Perhaps, an
.fossil-scm.org/fossil/info/9c211011190bde9a compiled with
either mingw32 or msvc2015.
Maybe you have a bad merge in your check-out. What does "fossil
changes" or "fossil diff" show?
On 11/5/16, Tony Papadimitriou wrote:
..\src\sqlite3.c(132731) : error C2143: syntax error : mis
..\src\sqlite3.c(132731) : error C2143: syntax error : missing ';' before '<<'
..\src\sqlite3.c(132758) : error C2143: syntax error : missing ')' before '->'
..\src\sqlite3.c(132758) : error C2143: syntax error : missing '{' before '->'
..\src\sqlite3.c(132758) : error C2059: syntax error : '->'
..
e wrote:
> On 2 November 2016 at 09:33, Tony Papadimitriou wrote:
>> c:\fossil\win\winhttp.h(24) : error C2004: expected 'defined(id)'
>> c:\fossil\win\winhttp.h(24) : fatal error C1012: unmatched parenthesis :
>> missing ')'
>> NMAKE : fatal error U10
c:\fossil\win\winhttp.h(24) : error C2004: expected 'defined(id)'
c:\fossil\win\winhttp.h(24) : fatal error C1012: unmatched parenthesis :
missing ')'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\BIN\cl.EXE"' : return code '0x2'
Stop.
I can compile fossil just fine (with or without SSL) with MSVC12
I just installed MSVC14 and I get errors when compiling with the SSL option (no
errors without it).
(BTW, SQLite3 also compiles OK with MSVC14).
So, I wonder if this is normal, or if I should be looking for installation /
configur
This is fossil version 1.36 [65e69b8dd8] 2016-10-24 18:15:07 UTC
Compiled on Oct 29 2016 19:57:38 using msc-18.00 (32-bit)
SQLite 3.15.0 2016-10-14 10:20:30 707875582f
Schema version 2015-01-24
zlib 1.2.8, loaded 1.2.8
SSL (OpenSSL 1.0.2j 26 Sep 2016)
UNICODE_COMMAND_LINE
STATIC_BUILD
Just to bri
atest trunk
On 9/19/16, Tony Papadimitriou wrote:
manifest_.c:2631: extra '#endif'.
tar_.c:708: Unterminated "{"
Errors while processing "tar_.c"
NMAKE : fatal error U1077: '.\makeheaders.exe' : return code '0x2'
Stop.
I'm unable to reproduce
manifest_.c:2631: extra '#endif'.
tar_.c:708: Unterminated "{"
Errors while processing "tar_.c"
NMAKE : fatal error U1077: '.\makeheaders.exe' : return code '0x2'
Stop.___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm
Rather than having an arbitrary fixed (20) default number of timeline entries
that get displayed with the console TIMELINE command, wouldn’t it be better to
have this number auto-adjust based on the actual number of rows the display
has. The default seems to be suitable for the classic 80x25 di
Hi,
I would like to see the changes introduced just by single check-in as applied
to the current (or even an arbitrary) version.
I suppose this would be the same as trying to see which lines would be affected
if I were to do a MERGE with the –BACKOUT option
A diff with –from and –to version sh
This is fossil version 1.35 [3aa86af6aa] 2016-06-14 11:10:39 UTC
It’d be less confusing if BISECT displayed the date/time the same way as the
current timeline setting.
Thanks.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists
ussion
Subject: Re: [fossil-users] FOSSIL does not push edit comment changes,is
this normal?
On 6/17/16, Tony Papadimitriou wrote:
This is fossil version 1.35 [3aa86af6aa] 2016-06-14 11:10:39 UTC
After editing a couple of check-in comments, I did ‘push’ and saw zero
artifacts sent. Here’s the
This is fossil version 1.35 [3aa86af6aa] 2016-06-14 11:10:39 UTC
After editing a couple of check-in comments, I did ‘push’ and saw zero
artifacts sent. Here’s the output:
Push to file://E:/db/xxx.fossil
Round-trips: 1 Artifacts sent: 0 received: 0
Push done, sent: 281962 received: 12407 ip
Hello,
In doing FOSSIL –GDIFF between two check-ins using the –FROM and –TO option of
the command,
I’m shown the files (left and right window in WinDiff) with auto-generated temp
filenames at the top for each side, respectively.
This makes it impossible to know which files I’m looking at, unles
When giving the set command to change some option and you’re outside an open
repo directory, the global setting is affected instead, even though the
–-global option is not given.
So, one can very easily mess up their global setup by accidentally attempting
to set a local option but either from
I've had the same wish for a long long time. I would like the FOSSIL BRANCH
list to show except for the branch name some kind of description.
Like you mentioned, making the branch name itself long enough would be one
way to tackle this but it is counter-productive as you would need to type
the
In case it applies to you, if you haven't rebuilt the repo since the mistake
shunning, I believe you can un-shun what was shunned, and it should all come
back to the way it was.
On 5/14/2016 4:59 PM, John P. Rouillard wrote:
I had to recently shun some artifacts from a fossil repo (due to embe
Possibly the best ‘color-blind proof’ method is reverse video. Not the best
looking in all cases, but certainly effective.
From: Scott Robison
Sent: Sunday, April 24, 2016 7:39 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Colored output on console
On Apr 24, 2016 4:07 AM, "
I don’t know if this will be of any help, but I moved away from using stash
altogether for pretty much the same reasons you mention, plus one very
important one for me that I don’t like about the stash: the content of the
stash only stays on the current PC while I wanted it to follow the repo fi
OK, thanks. Rereading the help it is now 'obvious' :)
-Original Message-
From: Richard Hipp
Sent: Tuesday, January 26, 2016 5:39 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL LS does not honor -R option
On 1/26/16, Tony Papadimitriou wrote:
I needed to see the file contents of a repo without opening it.
So, I tried the ls command with the –R repo option but I got an error message:
current directory is not within an open checkout
But, the –R option is listed in the help for the ls command.
Thanks.
With all this talk about how to keep draft work out of the repo when done with
it, I started playing with the various methods mentioned.
I noticed the following, and I would like to know if this expected behavior or
some bug.
Regardless, it is disturbing to lose trunk (or other branch) commits w
schrieb Richard Hipp :
On 11/17/15, Tony Papadimitriou wrote:
So, if you’re looking for the word ‘scroll’ it won’t match ‘scrolling’
and
vice versa.
"scroll" should match "scrolling" if you activate the "Porter Stemmer"
option
Or 's
ber 17, 2015 6:03 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL SEARCH improvement suggestion
On 11/17/15, Tony Papadimitriou wrote:
So, if you’re looking for the word ‘scroll’ it won’t match ‘scrolling’ and
vice versa.
"scroll" should match "scroll
When using SEARCH you need to type the word exactly as it appears in the
timeline.
I’m guessing it uses SQL’s LIKE to find the related matches.
So, if you’re looking for the word ‘scroll’ it won’t match ‘scrolling’ and vice
versa.
One suggestion is to append ‘%’ to the search term to match any
ov 13, 2015 8:20 AM, "Tony Papadimitriou" wrote:
>
> Here’s a merge conflict I thought should have been resolved automatically:
>
> I have the trunk version from where the symbol RF_OUT is renamed to SRF_OUT
> in the branch version. It has never been renamed to SRF_OU
t: Re: [fossil-users] Unexpected merge conflict
On Fri, Nov 13, 2015 at 4:20 PM, Tony Papadimitriou wrote:
<<<<<<< BEGIN MERGE CONFLICT: local copy shown first <<<<<<<<<<<<<<<
@?status RF
Here’s a merge conflict I thought should have been resolved automatically:
I have the trunk version from where the symbol RF_OUT is renamed to SRF_OUT in
the branch version. It has never been renamed to SRF_OUT in the trunk version
(yet).
When trying to merge (--cherrypick, actually) from trun
Thanks.
BTW, the help for clean shows this (which is a bit misleading):
--no-prompt This option disables prompting the user for input and
assumes an answer of 'No' for every question.
But, if prompting is disabled by default, how does that disable it further?
-Original Message-
)
-Original Message-
From: Andy Bradford
Sent: Thursday, October 22, 2015 7:36 AM
To: Tony Papadimitriou
Cc: Fossil SCM user's discussion
Subject: Re: [fossil-users] Questions about wiki linking to non-branch artifact
IDs/images
Thus said "Tony Papadimitriou" on Mon, 19 Oct 2015
36 AM, Richard Hipp wrote:
On 10/19/15, Tony Papadimitriou wrote:
My question is how can I add this image to the repo in a way that it is
not
part of any branch or ticket (e.g., attachment to a ticket)?
I only need it for the purpose of being shown in the wiki page but I do
not
want it to be part o
I’m trying to add an image to a wiki page. I want the image to be stored
inside the same fossil repo (i.e., not external link).
I read about all the possible ways one can create links with the [...] syntax.
For example, I can either use the artifact ID, or an image name.
My question is how ca
When restoring a previous version of a single file, is there any practical
difference between the following two actions:
fossil up version file
fossil rev -r version file
I have been using the UPDATE method up to now. But, I ran into the other
possibility in the docs and I wonder when each sho
stand
out from the rest.
-Original Message-
From: Andy Bradford
Sent: Thursday, October 01, 2015 5:20 PM
To: Tony Papadimitriou
Cc: Fossil SCM user's discussion
Subject: Re: [fossil-users] Suggestion for command-line timeline display
Thus said "Tony Papadimitriou" on T
Hello,
Not too long ago SQLite3 shell got a colored startup message about using
“transient in-memory database”.
I was wondering if the same idea could be used to highlight the *CURRENT* entry
in the timeline (with some soft color – a shade of blue or green would be nice).
This is because in a t
> I can do a manual UPDATE to bring each file in the working branch from trunk
> ‘by hand’ but shouldn’t a MERGE take care of that also?
Strike that out. I talked without testing it first. This does not work,
either. The file(s) reported as ‘not found’
From: Tony Papadimitriou
I’m in some branch and doing a MERGE from trunk.
Everything OK except for some newly added files on trunk that were not in the
current branch, but a merge was expected to deal with them also.
But, they do not ‘copy over’. The result is the project is incomplete as the
updated files depend (#inc
Is it possible to have an ‘FOSSIL ALL CLOSE’ command?
I usually have several unrelated fossils open at once. And because of working
on the same ones from work and home (and sometimes notebook), and how I
transfer backups back and forth at the end of the day, I *need* to close all
open fossils,
When doing:
f gdiff --from 2015-07-07
where the 2015-07-07 date is today, or any date later than the latest check-in,
I get a list that looks like the execution of a CHANGES command, which is is
certainly incorrect.
Thanks.___
fossil-users mailing li
Here’s the actual transcript of what I tried today, without success (on a Win7
machine):
C:\progs\lua\so>f mv 30689195_othershack.lua 30689195_others_hack.lua --hard
RENAME so/30689195_othershack.lua so/30689195_others_hack.
Hello,
Is there a way to see a ‘diff’ between two stashed ids, rather than stash to
disk?
Thanks.___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
This is on a Win7 machine (if it matters). A simple way to reproduce (f =
fossil):
f new xxx.fossil
f o xxx.fossil
mkdir a\a
dir > a\a\xxx
f add a
f com -m "Initial"
f mv a\a b
f close
Based on help screen, and usual behavior of mv, I would expect subdirectory a\a
to be now known as b, and of
It has its pros and cons. Most important ones I see:
+ Common files will only be stored once (having the same SHA) so overall
size of repos is smaller than the total of separate repos, one for each
project.
- If common files change, you need to merge changes to each project
separately, making
The way I solve this problem is to keep a repo of all projects that share
the same libraries together. This creates some other minor problems (that
were recently made less of a problem with the -p option enhancement of the
TIMELINE command.) But, I think this is the only reasonable way.
Ther
I use mostly Windows, but every so often I open the repo on a Linux box (but I
can do without Linux for now).
From: Richard Hipp
Sent: Monday, October 27, 2014 3:13 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL ALL
On Mon, Oct 27, 2014 at 6:58 AM,
I guess the same scenario would be valid if one used a server but had private
branches. My understanding is that private branches do not sync so the only
way to move to another location is to move the whole fossil file. Correct?
From: Tony Papadimitriou
Sent: Monday, October 27, 2014 1:48 PM
previous version
goto LOOP
From: Richard Hipp
Sent: Monday, October 27, 2014 1:11 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL ALL
On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou wrote:
I have several repos open at the same time, not always the same ones. Befo
Actually, FOSSIL ALL LIST shows all repos, including the closed ones. If it
only showed the open ones, half of my problem would be solved (although a new
one would be created – how to see all repos installed on a given machine).
Regarding the rest of your comments please see my response to Dr
I have several repos open at the same time, not always the same ones. Before I
swap computers (home <=> work) I would like to close all open repos on one
site, and take a backup to take to the other site.
But there is no easy way to find out which repos are currently open – so, I
must explicit
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FINFO suggestion
On Fri, Oct 17, 2014 at 8:34 AM, Tony Papadimitriou wrote:
Would that be too much programming effort to add? I.e., check if ‘filename’
is a directory and in that case return FINFO for all associated files.
FINFO (Usage: fossil finfo ?OPTIONS? FILENAME) is one of the most useful
features of fossil as it accepts a filename and provides its history of changes
(unfortunately, it does not follow possible file renames, but that’s another
issue).
What I would like is to have the possibility to also spec
I didn’t follow the whole conversation so I may be missing significant context.
I found that if you have several 0-length files and shun their (obviously)
common SHA1 does not remove any of them (apparently, because only the file name
is stored without any data, and the way I understand shunning
As a general observation, I would say that options is the ONLY option to
allow multiple mentalities to co-exist! And, I just proved it! :)
-Original Message-
From: Ramon Ribó
Sent: Friday, October 10, 2014 11:32 AM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] auto-sync
Chances are when you use FOSSIL_BUILD_SSL you also want to enable SSL.
So, to avoid having to give both FOSSIL_BUILD_SSL and FOSSIL_ENABLE_SSL on the
make command line, I propose something like this change in the win/Makefile.msc:
--- OLD ---
# Uncomment to enable SSL support
# FOSSIL_ENABLE_SSL =
When editing a ticket, the 'Subsystem' drop-down list is blank.
Question: How do I enter new values, or how do I define the possible values
from which to choose?
Since I keep multiple applications in a single repository (because they all
depend on common library code), I would like to use thi
I have some bad news and some good news. :)
I tried on Win7 32-bit, and I get the same error (and, yes, I used the
latest trunk and the new FOSSIL_BUILD_SSL=1 setting on the command line):
---
link /nologo /subsystem:console /opt:ref /debug
/out:out32\md4test.exe @C:\Us
Hi,
First, a minor bug in the CAT command (on Win machine): Using a backslash in
the path does not find the file, while using a forward slash finds it.
Second, would it be possible to add the "-R repo_file" option to the LS
command? It'd be nice to get the list of files without opening the r
1 - 100 of 124 matches
Mail list logo
