hen you can just use our wonderful hodgepodge of HTML and quirky
custom extensions?" as a response.
I'd add these examples to my blog post that demonstrates their bugs, but
I fear what it might do... ;-)
--
Ross Berteig r...@cheshireeng.com
Ch
the
bug is actually in the test case. We really ought to make some time to
review every use of "knownBug".
If tester.tcl is invoked with the -strict flag, then tests marked
knownBug that succeeded count as failures to draw attention to a known
bug that got fixed.
--
Ross Berteig
On 7/12/2017 2:08 PM, Ross Berteig wrote:
On 7/12/2017 11:50 AM, Richard Hipp wrote:
The current plan is to release the 10th anniversary edition of Fossil,
version 2.3, on 2017-07-21.
I will dust off my test-maven hat and see what happens with clean
builds tortured by the test suite
https://core.tcl.tk/
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http
ff I have here on my Windows box (version 2.8.7 built in 2004
apparently) does not have such an option. Read about "fossil set
diff-command" for how to do that.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.Ch
tended for use by automation that
wants to consume JSON, attempting to guarantee that any access within
that namespace will be HTTP 200 with a JSON packet explaining the API
call results seems reasonable.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineerin
On 6/9/2017 1:21 PM, Warren Young wrote:
On Jun 9, 2017, at 12:17 PM, Ross Berteig <r...@cheshireeng.com> wrote:
I do think that the JSON support is close to solid enough to be on by default.
For functionality alone, that is surely true, but in the face of malice?
Parsers are notor
On 6/8/2017 9:17 PM, Stephan Beal wrote:
On Thu, Jun 8, 2017 at 10:43 PM, Ross Berteig <r...@cheshireeng.com
<mailto:r...@cheshireeng.com>> wrote:
For building tools to generally interact with a repo, take a look
at the JSON support. It's (still) not compiled i
hout requiring a lot of work for new versions.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
appears to
work on any number of table columns without any coding changes.
I like the idea in general. It could completely eliminate the need for
cron jobs to generate an index file, without a huge amount of
configuration work.
--
Ross Berteig r
not a symbolic link because the chroot jail won't allow the
link to be followed).
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users maili
lued options...
And I don't want to make my build and test automation depend too much on
which version it is building. That is the whole point of using autosetup!
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
d needed on disk to move the current
working copy to revision xxx. It isn't an edit. You simply have a check
out at that revision level. This is a command that is frequently used to
hop between trunk and branches, or to go back to a version that has a
bug report to reproduce it locally in exact
On 5/10/2017 1:12 PM, Tony Papadimitriou wrote:
So, ignore ‘makefile’?
*From:* Ross Berteig <mailto:r...@cheshireeng.com>
# ignore files without at least one dot somewhere in their name
!*.*
Yup. It would do that. And README, LICENSE, CHANGELOG. Not without its
problems. But
f the REGEX operator is
enabled in fossil's loaded SQLite.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists
d I personally never use is "fossil close". It exists at all
for symmetry with "fossil open", and to clean up a database entry in
your master list of open repositories that will be subject to "fossil
all". But I've never found that to be a co
.
No, the wild cards in the glob can match any part of the path. You can
ignore "*/_build/*" and that will ignore any folder named _build and all
its descendants anywhere in the tree except at the root of the workspace.
--
Ross Berteig r...@cheshireeng.co
someone who wants
to delve into the fossil codebase. I would, but I'm *way*
over-committed at the moment.
As usual, a working patch adds a *lot* of weight to an argument for a
feature.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp.
ion. Probably should
do that anyway, it can help you locate where in the timeline you
introduced a particular version.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.
to bring the new library version and all the integration effort over to
trunk.
Naturally, this keeps the older versions on hand, but since they built
older versions of your project, that helps keep it all straight for
later maintenance and patching.
--
Ross Berteig
nfusion when
experimenting with this:
C:\Users\Ross\Documents\tmp\fossil4>fossil test-echo *.no-such-file.*
g.nameOfExe = [C:\Programs\Bin\fossil.exe]
argv[0] = [fossil]
argv[1] = [test-echo]
argv[2] = [*.no-such-file.*]
C:\Users\Ross\Documents\tmp\fossil4>
--
Ross Berteig
hedding. Also, sadly, no
changes. It doesn't help that MS has been changing what they do in edge
cases from release to release, making it even harder to figure out what
to do to build code that does what you assume you wanted.
--
Ross Berteig r...@cheshireeng.com
Chesh
://www.sqlite.org/src/artifact/9d52522cc8ae7f5c?ln=616-631
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lis
On 4/11/2017 3:24 PM, Thomas wrote:
On 2017-04-11 23:09, Ross Berteig wrote:
On 4/10/2017 11:48 AM, Thomas wrote:
Actually, I got a batch file that reads the file filter settings from
another file and creates the binary-glob and the ignore-glob files on
the fly before an addremove
.
Comments are probably easy, but I suspect the glob syntax is tied to
SQLite. I may look into that.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil
ccidental tracking.
The --ignore switch is documented to "Ignore files matching patterns
from the comma separated list of glob patterns." And that is exactly
what it does. The fossil addremove command does not touch those files
either on disk or in the repository. It igno
ings
or a specific repository.
4. Use SQL to edit the setting into the repo file. Don't do this unless
you know what you are doing. The hint I'll provide is that the
repository is actually a SQLite database file. There is documentation.
But directly poking it is dangerous, so only try on a backu
lf-glob is to use versionable
settings for them. Then you get to edit a file rather than fighting with
strange shell quoting rules. Just create the file
.fossil-settings\crlf-glob in the root of your repository's workspace
and put a single line in it containing the asterisk. Ad
e of constraints.
But I won't recommend you try it at home.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fos
and lessons learned from the Linux
community which has been blazing that trail and found (and escaped) most
of the dead ends. I think it has become clear that Unicode is here to
stay, and UTF-8 is the best representation of it both at rest in files
and on the wire in protocol
type ActiveTclScript
ActiveTclScript="C:\Programs\Tcl\bin\wish86.exe" "%1" %*
You can change the definition of ActiveTclScript to include -encoding utf-8
Note that would make your installation less consistent with the rest of
the users, and is thus like
On 3/27/2017 6:21 PM, Richard Hipp wrote:
On 3/27/17, Ross Berteig <r...@cheshireeng.com> wrote:
I believe that a line is too long if it is more than about 8191 ASCII
characters, a restriction based on the size of the buffer used in the
diff engine.
Technically, that restriction
by older Macs.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org
uestion is about 3.3 megabytes in size, and as far as I
am aware, a normal plain-text org-mode file.
Any ideas would be very appreciated!
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.Ch
ial builds.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:80
ence much less my opinions.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.Cheshi
On 3/14/2017 3:06 PM, Stefan Bellon wrote:
On Mon, 13 Mar, Ross Berteig wrote:
When fossil is configured to include JSON support it has a fossil
json command that consumes a JSON object full of command and
arguments and returns a JSON object of results. A similar feature is
available over
Also, not every command is available via JSON, and I suspect that there
is no JSON equivalent to fossil annotate. If we can figure out how to
represent the annotate/blame/praise data in JSON, then adding it should
be possible.
--
Ross Berteig r...@cheshireeng.com
ssue. Now fossil update trunk
succeeds.
So to move an existing project to the latest fossil after an SHA3-named
artifact exists, it appears to be necessary to rebuild existing repos
with version 2.0 or later so the database schema don't include a
constraint that forbids SHA3 names.
ing a new kind of tag that can be
matched by prefix for the purpose.
-- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp.
http://www.CheshireEng.com/ +1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lis
eckin is stored in the D card of the checkin's
manifest, so it is not possible to edit it directly without changing the
SHA1 hash of the checkin.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
about pure
documentation.
[1] https://www.fossil-scm.org/index.html/doc/trunk/www/contribute.wiki
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-use
nce. We support fossil because it is useful to us. You
approach us with a hostile attitude, then get worse when people engage
and try to help.
4. The rest of this email which I'm not responding to in detail.
--
Ross Berteig r...@cheshireeng.com
Cheshire En
. Back in the
day, they used to insist on setting PATH, and then adding INCLUDE and
LIB which often messed with other compilers, even other compilers
targeting Windows let alone cross compilers.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp.
in the long run.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org
On 10/5/2016 3:27 PM, Richard Hipp wrote:
On 10/5/16, Ross Berteig <r...@cheshireeng.com> wrote:
Note that building for 64-bit needs something trickier than just
following that recipe from a 64-bit VisualStudio prompt.
Really? Because just typing "nmake /f makefile.msc&quo
for the complete list.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossi
d a folder named aux that was bit by this issue, and IIRC they
ultimately resolved it by renaming the folder to something that worked
on all platforms. I'm not recalling what project that was, though.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering
rough a badly thought out device driver) to create more such names.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Ross Berteig
empted to do that as an experiment.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.or
per-file tagging, you could have a build script
that verifies the "immutable" files have not mutated, and then require
that script be edited if a reason to update the immutable data is
discovered.
--
Ross Berteig r...@cheshireeng.com
Cheshire
curiosity (despite what that
does to cats) and try to understand it one of these days.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users ma
06-22.
I could see rewording the text for --force to be a little more succinct
and not imply something that contradicts the paragraph above it. But all
in all, this is pretty clear, IMHO.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www
finfo)
and also the silent switch -q as 2nd aka for compatibility with
GNU/diff --brief?
Thanks for your time and work!
Best regards,
Kain
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/m
On 8/10/2016 11:43 AM, jungle Boogie wrote:
If I have a repo syncing to example.com and I want to change it to
sync locally on my network, what's the best method to update the sync
url?
Set the url:fossil remote-url http://new-url-here.local/
Turn off sync: fossil remote-url off
--
Ross
On 8/6/2016 12:02 PM, Jan Danielsson wrote:
On 05/08/16 02:51, Ross Berteig wrote:
Many thanks; this saved me a lot of time, as a non-native tcl
speaker. And as such, I also would like someone to quickly look over
the additions I've made. It seems to work, but I have a feeling I have
have
On 8/4/2016 2:33 PM, Ross Berteig wrote:
I just built it and ran the existing test suite over it on Windows. It
passes all existing tests. I didn't spot any test cases for the new
feature
I just created test cases for fossil set manifest that verify that the
files manifest, manifest.uuid
oks and crannies in the fossil source kit.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.o
is would be less of a concern.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://list
d reasonable for it to pick a
preferred line ending and convert to it from entry and from it on display.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
and safely stowed in the local repository. There is no "roll back" from
that.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users
tcllib, as packaged
and delivered by ActiveTcl's teacup utility.
https://www.fossil-scm.org/index.html/artifact/65f8333164e4?txt=1=33-38
On linux, you'll have to find your own way to get the library, IIRC I
was able to tease it out of apt-get, but I don't recall what its name w
ly see such files as newly added at the time of the copy
while letting a new version also track the history across that event.
I'm not steeped enough in the manifest details to know what is possible
myself, however.
--
Ross Berteig r...@cheshireeng.com
Ch
name.
I'd argue the two displays should agree. I'm not sure at the moment
which display of the timeline is "correct".
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 62
ould be trickier. But a
way to do that would be to serve different clones to each user, and use
a cron job to keep them all synced. Probably not worth the effort unless
the value added to the user's convenience is significant.
--
Ross Berteig r...@cheshireeng.com
Cheshire
ick. But the difficulty is likely deciding when to add it. And
then hoping no one needed proper handling of cases for anything other
than 7-bit ASCII letters.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp.
ed
junk provided by SOC vendors without which it is often impossible to
build their sample code or even cross compile for their platform without
a whole lot of reverse engineering of their tool chain.>>
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineer
"isLeaf":true,
"timestamp":1460254449,
"user":"andygoth",
"comment":"Merge trunk.",
"parents
ould probably also say that "--latest" and "latest" are the same
thing. As it is worded now, the two ways of describing it seem to hint
at a difference that isn't there.
I'll take a crack at rewriting that "soon", but if anyone else has ideas
I'm all ears
On 4/4/2016 11:33 AM, Ross Berteig wrote:
On 4/2/2016 3:40 AM, Svyatoslav Mishyn wrote:
But why that commit [b6b50b12] is marked
as *FORK* in timeline.rss;
and as *BRANCH* in `fossil timeline`;
while here https://www.fossil-scm.org/index.html/info/b6b50b1244796110
looks like usual commit
On 4/2/2016 3:40 AM, Svyatoslav Mishyn wrote:
(Fri, 01 Apr 17:50) Ross Berteig:
Even better, Joe has already done that to trunk.
But why that commit [b6b50b12] is marked
as *FORK* in timeline.rss;
and as *BRANCH* in `fossil timeline`;
while here https://www.fossil-scm.org/index.html/info
On 4/1/2016 7:14 PM, Warren Young wrote:
On Apr 1, 2016, at 7:13 PM, Warren Young <w...@etr-usa.com> wrote:
On Apr 1, 2016, at 6:50 PM, Ross Berteig <r...@cheshireeng.com>
wrote:
may I recommend just reading /test-all-help cover to cover once
in a while?
Okay. Back in a few…
On 4/1/2016 6:13 PM, Warren Young wrote:
On Apr 1, 2016, at 6:50 PM, Ross Berteig <r...@cheshireeng.com> wrote:
...
* "mtime" or "modification time”?
That one’s different, with a much stronger claim: man 2 stat.
That is, it is a ~45-year old term of art, not a neologism.
neologism as a jargon term with
an exact meaning in this context is probably good. On the other, where
plain English would do just as well, it probably should be preferred.
* "webpage" or "web page"?
* "filename" or "file name"?
*
On 3/7/2016 12:39 PM, Joe Mistachkin wrote:
Ross Berteig wrote:
I don't think that is needed any more?
$ fossil open ../fossil.fossil
$ ./configure --with-miniz --with-openssl=none
$ make test"
In an open checkout: cannot initialize a new repository here.
while executing
&
st/amend.test" line 52)
I updated main.mk (via makemake.tcl) and checked that in.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing l
a decent confidence level that most fossil features are touched. We
haven't reached that goal completely, but this is a strong step along
the way.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 62
will be using it to debug an
issue in the fossil json test cases "real soon now".
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-use
FOSSIL_TEST_TEMP,
FOSSIL_TEMP, TEMP, or TMP with each checked as all caps, all lowercase,
and initial caps) to force it to land somewhere known. Also use -keep
(which certainly should cause it to print the location of the clutter)
to keep the clutter around for post-mortem fuss
On 3/3/2016 11:34 AM, Andy Bradford wrote:
I'll see if I can track it down later if there is no more progress
elsewhere.
Try setting TEMP somewhere sane, perhaps:
$ export TEMP=/tmp
$ tclsh
That fixed it for me.
--
Ross Berteig r
On 3/3/2016 10:53 AM, Joe Mistachkin wrote:
Ross Berteig wrote:
My Ubuntu VM saw this exact message. I was running tester.tcl in a
testing folder that is neither the build nor source tree.
My guess is that you had a pre-existing checkout recorded for that
directory. Please "fossi
today. But I'm hoping that between Andy's and my reports of
failure, that someone much more versed in the subtleties of
cross-platform Tcl will spot the mistake.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626
her than root when
serving files, which is exactly what would normally happen if fossil
were accessed via CGI since web servers are usually not running as root.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626
ttps://www.fossil-scm.org/index.html/artifact/e75796be5338a81c?ln=1463,1523
That function is called in "fossil http", "fossil server", and "fossil
ui", also implemented in main.c.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engin
bled?
--
Joe Mistachkin
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fos
.
So it looks like that was a six character edit to the amend command. Try
checkin [769bc7b4] as see if it does what you expected.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
. I have several more folders just like
it (built with different configurations).
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
___
fossil-users mailing list
fossil-users@l
On 2/17/2016 6:54 PM, Andy Bradford wrote:
Thus said Ross Berteig on Wed, 17 Feb 2016 15:18:12 -0800:
fossil mv --hard old new; touch old; fossil stash -m "both" fails to
stash with the SQLITE_CONSTRAINT message.
Not for me...
$ f ver
This is fossil version 1.35 [7ad8230273]
cause fossil stash diff to complain. The stash
currently is quite touchy about renamed and deleted files.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
On 2/15/2016 10:19 PM, Andy Bradford wrote:
Thus said Ross Berteig on Mon, 15 Feb 2016 12:09:26 -0800:
I've been seeing that same message on Windows, specifically in the
context of test stash-2-1. The changeset being stashed includes a
renamed file and an added file that uses
of test stash-2-1. The changeset being stashed includes a
renamed file and an added file that uses the renamed file's original name.
Notably, fossil revert passes given the conditions.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http
On 2/12/2016 8:45 AM, Warren Young wrote:
While doing the tests detailed in my other thread (delta.c assertion
failure on Linux) I came across two other oddities that seem like
unrelated issues, so I’m starting a new thread for them.
I think Ross Berteig ran into some of this, so please
On 2/12/2016 9:02 PM, Andy Bradford wrote:
Thus said Ross Berteig on Fri, 12 Feb 2016 11:53:38 -0800:
2. The file rename is not rescheduled. It says:
MISSINGzip.c
Reproduced in the test case. Which I will commit any minute now.
I saw this too a couple days ago and began working
On 2/12/2016 5:39 PM, Warren Young wrote:
On Feb 12, 2016, at 5:09 PM, Ross Berteig <r...@cheshireeng.com>
wrote:
After considering, I strongly suspect this is by design.
Of course; reverting add should not remove the file. The file was
not always Fossil’s to do with as it pleas
On 2/12/2016 11:53 AM, Ross Berteig wrote:
While comparing to a similar sequence with an added f3 instead of a
rename, I noticed another anomaly which I will try to paint into a
corner next.
Ok, I chased this into a corner with a test case, and got all the way to
the corner apparently
On 2/11/2016 10:06 AM, Ross Berteig wrote:
What does fossil revert do in this circumstance?
It says:
REVERT f1
DELETE f1new
"fossil undo" is available to undo changes to the working checkout.
and has now forgotten the pending rename.
I think that fossil stash save *
and support
everything else he's touched *without aggravating his elbow.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
___
fossil-users mailing list
On 2/10/2016 10:41 PM, Andy Bradford wrote:
Thus said Ross Berteig on Wed, 10 Feb 2016 15:48:40 -0800:
which as expected renamed the file in the repository but not on the
disk. It then says
fossil stash -m "B 2016-02-09"
Did you mean:
fossil stash save -m "B 20
ch file: c:/Users/Ross/Documents/tmp/fbuild/stash/f1new
and does not create any stash entry.
What was fossil stash supposed to do in this circumstance? The early
test case (modeled after fossil revert's behavior) modeled the stashed
rename oddly as well, but at least it did model it.
--
Ro
1 - 100 of 196 matches
Mail list logo
