Hi all,
I would like to add older code (kept manually until now in ZIP files) to a
fossil repository already containing some newer versions. Is there a way to
add older versions manually, perhaps by specifying the date via a command
switch, or by using the actual file dates for each of the fil
Hi all,
Like the subject says: Is it possible to restore the original file dates
whenever reverting / updating to a given version?
This is important for MAKE files to not consider a file updated and try to
rebuild.
TIA___
fossil-users mailing list
fo
On the other hand, when updating to a previous version, you’re actually
interested in getting a snapshot of how things were at that time, and if every
restored file is given a ‘now’ timestamp, using MAKE is the equivalent of
always using the –B option, which is not likely what you wanted to do.
Example (where f = fossil):
f rev
f undo (OK)
...
f rev
f rev (NO CHANGES, apparently)
f undo (nothing happens)
This does not seem to be right. Because if by mistake you type “f rev” twice
(not being sure if you’ve already done it) you lose the ability to undo.
Thanks.
Is there a direct way to see differences for a specific file from the last time
this file actually changed, regardless of version?
(where f = fossil)
Something like: f diff file --from prev
but where prev would refer to the previous changed version of this particular
file, not just the previous
Fine, but I don’t think this would require a multi-level undo stack. A simple
flag to indicate at the completion of any command if anything has changed
(i.e., files written, deleted, or renamed) during its execution would be enough
to decide whether to clear the one-level stack or leave it as i
But there are some problems (This is fossil version 1.29 [003db810a2]
2014-04-30 18:02:45 UTC):
fossil test-name-changes -R \db\some.fossil prev trunk
Assertion failed: e>0, file ..\src\bag.c, line 122
Stephan Beal wrote:
On Wed, Apr 30, 2014 at 11:02 PM, j. van den hoff
wrote:
just a shor
Couldn’t this also be used to solve another problem, that of keeping separate
repos for various projects that depend on (sometimes massive) common library
files? Currently to deal with that I have to put all projects under the same
repo, which is not ideal. The alternative, keeping multiple co
Does fossil support or has plans to support autocrlf (like Git)?
(Text files internally saved always with Linux line endings, but extracted as
Win, Linux, Mac line endings depending on the platform FOSSIL runs on)___
fossil-users mailing list
fossil-use
I know about crnl-glob. But it is a completely different issue than autocrlf
(like with Git).
As for the hash mismatch this is just a minor technical issue easily solved.
The hash would have to calculated after stripping off all CRs (Win/DOS) or
converting to LFs (Macs) in text files. Then i
Well, I can give a couple of personal examples that you easily try yourselves:
* Windows side: Copy/Paste in Windows can not deal with LF endings correctly.
Example: PNotepad editor in Windows loads Linux files but copy-pasting from it
(for example) to other apps messes up all text (puts it all
From: Scott Robison
Sent: Sunday, June 08, 2014 12:05 AM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] autocrlf like in Git?
* Several old time assemblers will choke on wrong line endings. Their
binaries cannot be updated as the source is no longer available. So, you
must edit
From: Scott Robison
Sent: Sunday, June 08, 2014 12:58 AM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] autocrlf like in Git?
> I completely agree with the points other than the one that "the DVCS is the
> only tool that can effectively manage the EOL convention of the files". I u
Hi all,
It seems to me that commits are best (from a logical point of view) when they
refer to completed work, not for work-in-progress (WIP). Besides, it’s not
nice to see a timeline filled with incomplete non-working code. For example, I
create a new library code file that is under initial
I think your suggestion would work fine under some conditions:
1. You always use a top-down design methodology.
2. Your whole repo is a single project.
(1) If you have a bottom-up design (e.g., first design the library, and when
you get it working, integrate it into the main app), you’ll never s
Private branches? I don't know, I'll give that a try.
Thanks for your suggestion.
Questions (to all):
1. If the only way is to use a special branch to do what I need, can at
least a single branch be reused multiple times? I mean the same branch name
(e.g., the WIP branch) to be created, clo
Well, maybe my ideas are wrong for you, but I assure you, to me they always
seem very right! :) Just like programming styles, mine *may* be very wrong to
many, but it's the best there is to me, and has never let me down!
But at least we agree on committing those work-in-progress files on some
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 op
FOSSIL DIFF --BRIEF shows a list of files that changed.
FOSSIL GDIFF --BRIEF seems to ignore the brief option.
They share a common help screen where the option is available presumably to
both.___
fossil-users mailing list
fossil-users@lists.fossil-scm.or
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
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) can
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 sol
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 equal
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.
[2
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 differences
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:
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 fil
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 f
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:
--
C:
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: to...@acm.o
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. Sin
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 about
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 of
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 6
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 show
(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 a
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: [fossil-users
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 sin
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 t
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 seems
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 S
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
change
OK, here's one more minor issue you can easily test with sqlite3 repo under
Windows. Windows filenames are case insensitive. Trying with wrong case
fossil tim readme.md -R sqlite3.fossil
+++ no more data (0) +++
while, trying with correct case
fossil tim README.md -R sqlite3.fossil
=== 2
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
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
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
http://lists.fossil-scm.org:8080/cgi-
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
http:/
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 FILENAM
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 keyw
:01:55 [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
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: Stef
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 to
Regarding (1), I thought a bit more about it and it won't work because
except for tag names you also have dates, and it is conceivable that a
subdirectory name looks like a date (e.g., 2014-10-01), so checking the tag
list is not enough to disambiguate.
Regarding (2), we agree. I find it less
On Sun, Oct 19, 2014 at 10:14 AM, Stefan Bellon 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 the consensus is f
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
>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! )___
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 on
(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 fail
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: Kee
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 be
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
it
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
http://li
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
Subjec
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, bu
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
exa
-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.
How about this idea?
During 'commit' when asked
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:
contains binary data. Use --no-warn
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
fossil-users@list
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 -DL_E
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
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 f
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
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=ci&nomo=0
(2) https://ww
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 com
++1
From: Scott Robison
Sent: Friday, March 20, 2015 11:08 PM
On Fri, Mar 20, 2015 at 2:55 PM, Steve Stefanovich 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.
Now that wou
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 pr
+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 li
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-
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, i
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 t
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
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 t
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 c
+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 on
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 don’t
..\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
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listi
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
..\src\url.c(485
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 `si
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 f
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)
U
(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: https://www.dropbox.com/s/ozzicm164dc2o0d/fork
FOSSIL MERGE would have been my guess too but it gives this message:
"Merge skipped because it is a no-op. Use --force to override."
And, using --force does nothing, of course. So, the timeline is still the
same. But, come to think of it, fossil merge should logically fix the
problem, even
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 up-t
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 itsel
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-
From
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
fos
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
neve
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
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: R
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
1 - 100 of 122 matches
Mail list logo
