Is there any way to find all the artifacts that correspond to a given
pathname? Then I could shun those.
On 26 July 2016 at 16:51, Richard Hipp wrote:
> On 7/26/16, David Mason wrote:
> > I have a problem.
> >
> > I use fossil for my courses - one I've used
On 26 July 2016 at 17:13, Richard Hipp wrote:
> SELECT DISTINCT uuid
> FROM blob, mlink, filename
>
Works a charm (18 UUIDs show up). Now if there were a way to shun from the
command line, I'd be golden.
BTW, swapping "uuid" and "filename.name" in the SQL lists the files that
match a uuid.
identally trimmed when there are no other repos available
> with which to sink. Perhaps the trimmed content gets written into a
> separate "trash-can" database?
>
> On 7/26/16, David Mason wrote:
> > I have a problem.
> >
> > I use fossil for my courses - one
I's about 1/3 of the way through this report:
https://groups.google.com/forum/#!topic/mozilla.dev.version-control/nh4fITFlEMk
It seems that they originally preferred GIT (because it was what they knew)
but now prefer hg, although it's a bit light on the reasons. The article
points out that Facebo
Richard and Warren both make very legitimate comments. I wasn't seriously
suggesting that work should stop moving Fossil forward for the perhaps
marginal benefit of conversion to Rust.
However, the value of Rust is not simply memory management. The
*considerably* more expressive type system, and
On 11 April 2017 at 14:34, Scott Robison wrote:
> No, it is an explicit command clearly stating the user's desire for
> exclusion of these files *that are not already under source control*.
> The fact that the user does not remember or did not realize they
> issues conflicting commands does not m
I've been using fossil for several years now, so when I set up a new fossil
my first operation is to copy over an existing .fossil-settings and commit,
so I haven't been exposed to this problem for a while. I certainly
remember when I first used it that it did some unexpected things. Perhaps
if th
Another option is to create a fossil for the 3rd party libraries, and then
open that fossil --nested in a directory inside your working directory.
Then nothing in that nested directory tree will be part of the main
fossil. You don't even need to commit to it if you don't want. Lastly,
when you do
I have had to use Git for something this semester. It was mostly a failure
and I'll find a way to use fossil going forward.
That said, I noticed one feature of Git that was very useful, and I'd love
to see in Fossil. In Git, you can have a .gitignore file in any directory
and it applies to that
On 18 April 2017 at 18:04, Ross Berteig wrote:
>
> 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.
But if I want to *not*
I bought this, largely to support the Fossil community (because I don't use
Finder much, but this might change my workflow), and a couple of points:
1) the docs are wrong... to add a working directory you need to go to
SnailFossil preferences.
2) The right-click to commit doesn't do anything for
On 7 May 2017 at 12:20, John Pateman wrote:
>
> The right click commit seems to work fine in Sierra. You need to add the
> checkout directory to the list that SnailFossil is tracking. The files that
> are synced up should all have a green tick badge. Adding a new file to the
> checkout folder sho
I have a fossil repo and in it I have a file foo.js that is generated by my
build process - so I don't want it versioned. But I *do* want it
distributed, and want it referencable from foo.html - which *is* versioned.
foo.html and foo.js are *not* served by fossil, but by a simple apache or
nginx se
I've described before how I use fossil to manage student assignment
submissions in courses I teach.
A perennial problem is that the students commit binary executables, .o
files, and the like. Theses change every build so I have dozens of versions
of potentially large files in the student repos. D
Perfect! I knew it would be easy.
Thanks
On 10 May 2017 at 07:04, Richard Hipp wrote:
> On 5/10/17, David Mason wrote:
> > I have a fossil repo and in it I have a file foo.js that is generated by
> my
> > build process - so I don't want it versioned. But I *do* want
when
they first clone the repo their local repo gets the configuration.
../Dave
On 10 May 2017 at 07:11, Richard Hipp wrote:
> On 5/10/17, David Mason wrote:
> > I've described before how I use fossil to manage student assignment
> > submissions in courses I teach.
>
Bradford wrote:
> Thus said David Mason on Wed, 10 May 2017 01:07:22 -0400:
>
> > If the students were very disciplined, they would assiduously edit
> > ignore-glob to prevent this. But if there is one thing that students
> > (en-mass) are not, it's disciplined!
>
On 10 May 2017 at 17:05, Artur Shepilko wrote:
> Not sure about the objectives the students are learning in this
> course, but if it in any way relates to programming, recognizing as
> to what to keep under version control is a reasonable objective on its
> own.
>
While I might agree, and the t
You can have a working directory for one repository nested inside a folder in a
working directory of another repository. See the —nested option for `fossil
open`.
I use this *extensively*. It’s very convenient. But it may not be quite what
you want because you do have to commit separately for
`fossil unver revert`). It's good that cat
works, but revert seems nicer!
Thanks ../Dave
On 10 May 2017 at 09:34, David Mason wrote:
> Perfect! I knew it would be easy.
>
> Thanks
>
> On 10 May 2017 at 07:04, Richard Hipp wrote:
>
>> On 5/10/17, David Mason wrote:
files?
Thanks ../Dave
On 14 June 2017 at 01:32, David Mason wrote:
> I finally got around to this, but I got the following errors on Linux:
> : ~/Sites/p4ru/kitPJS ; fossil unversioned revert
> Usage: fossil sync URL
> : ~/Sites/p4ru/kitPJS ; fossil ver
> This is fossil version 2
n 14 June 2017 at 01:41, David Mason wrote:
> `fossil uv list` doesn't mention any path information. Does it have path
> information behind the scenes so that `fossil uv revert` can put the file
> in the original place?
>
> Is there a way to find if any unversioned file has
Wow... longest thread I've ever seen. I scanned through and didn't see
mention of the simplest solution, if you have shasum available.
> shasum urltags.js
1bea11bf4a97b012e7d8b17c71a7d444f0b5a5aa
> fossil ui
Then go to localhost:8081/artifact/1bea11bf4a97b012e7d8b17c71a7d444f0b5a5aa
and you'll g
It is unclear from the documentation what this switch actually does, and I
unfortunately do not have time at the moment to read the code.
I use Linux and MacOSX and use symlinks to directories very heavily, so am
a little worried about what this change does. I never explicitly use this
switch.
I
I've seen it too, but it's sporadic. My crontab pull script now checks if
the size is 0 and ignores the file if so.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-
On 29 August 2017 at 23:55, Andy Goth wrote:
> I'm curious how the Markdown formatter would know what language rules to
> use for syntax highlighting, so surely there's more to the syntax than
> bracketing ("fencing") the code with lines consisting entirely of "```".
> I searched online and found
On 8 September 2017 at 10:47, Thomas wrote:
> If I do this I can never use addremove again. The checkin script runs
> addremove automatically each time.
>
If it's in the ignore-glob file, addremove won't add it. So put in the
ignore-glob, remove it once, clean up the shun, commit, and then what
I am trying things differently this year. I want to use one instance of
fossil running proxied behind a firewall. I have the following in my
Apache conf file:
ProxyPass http://127.0.0.1:8081
ProxyPassReverse http://127.0.0.1:8081
SetOutputFilter proxy-html
On 25 September 2017 at 13:59, Richard Hipp wrote:
> On 9/25/17, David Mason wrote:
> > I am trying things differently this year. I want to use one instance of
> > fossil running proxied behind a firewall. I have the following in my
> > Apache conf file:
> >
>
On 26 September 2017 at 06:30, Richard Hipp wrote:
> On 9/26/17, David Mason wrote:
> > if I try:
> >fossil clone
> > https://dmason%40ryerson...@cps506.scs.ryerson.ca/fossil/
> f2017/A-dmason_ryerson.ca.fossil
> > foo.fossil
> > it prompts for pass
hough obviously you won't be changing it!!!
Thanks again (both for the immediate help, and for fossil itself)!
../Dave
On 26 September 2017 at 10:05, Richard Hipp wrote:
> On 9/26/17, David Mason wrote:
> > Indeed! Thanks... I already noted that in the web access, but the file
> d
to create fossils on the fly
and change permissions/passwords, etc.
Thanks
On 26 September 2017 at 12:01, David Mason wrote:
> This is proxy, not CGI, but the same appears to apply:
>
> fossil clone http://dmason%40ryerson.ca@localhost:8081/f2017/A-dmason_
> ryerson.ca x.fossil
>
r
the record this is Linux.
Thanks ../Dave
On 28 September 2017 at 06:37, Richard Hipp wrote:
> On 9/28/17, David Mason wrote:
> >
> > I need to create fossils on the fly [using CGI]
>
> Fossil does not (currently) have that capability.
>
> What you are really asking for i
On 28 September 2017 at 07:37, David Mason wrote:
> I wasn't clear! (I've been working all night on this so it's
> understandable.)
>
> I have all the logic I need I just want fossil to behave like it would
> at a terminal prompt, rather than acting like a CGI... the
No, just setuid something other than www - an ordinary user.
I'm currently doing a workaround to not run fossil from within a CGI, but
it's not optimal (exposes some information I'd rather not expose).
Thanks
On 28 September 2017 at 09:26, Richard Hipp wrote:
> On 9/28/17,
sword (for obvious
reasons). Are there any other restrictions on the repo name or other parts
of the URL?
Thanks ../Dave
On 28 September 2017 at 09:53, Roy Keene wrote:
> On Thu, 28 Sep 2017, Mark Janssen wrote:
>
>
>>
>> On 28 Sep 2017 13:37, "David Mason"
16:04, Richard Hipp wrote:
> On 9/28/17, David Mason wrote:
> >
> > Last question for a while: in clone.c line 104 it says to use %40, %2f
> and
> > %3a for special characters in the userid and password (for obvious
> > reasons). Are there any other restrictions on
Also as a mere fossil user, I would find it useful if fossil could respond
to a git client and serve files. I use Pharo, which is working toward
integrated support for git, but I'd much rather trust my bits to Fossil.
While the Fossil UI is nice, I see much less value in using a local Fossil
to acc
I like the B cases... in fact I'd indent the details a bit so that the
comments are easier to find visually.
On 24 November 2017 at 11:53, wrote:
> I understand the need for links, but do users really need truncated hashes
> for every line?
> Can the link be applied more subtly?
> Can there be a
1) Add/remove a class to an enclosing DIV. You can see a very simple
version that I wrote in action on https://programmingfortherestofus.com
click on the bullets under Elevator Pitch.
2) Include all the content, just don't display it by default... dynamically
downloading additional content is almo
:ellipsis;
}
The optional expand parameter to toggleExpand is if you want to add a
different class when it's expanded. I use it elsewhere, but not here.
../Dave
On 25 November 2017 at 09:38, David Mason wrote:
> 1) Add/remove a class to an enclosing DIV. You can see a very simple
>
Looks good.
When I did that, I made clicking on anywhere in that div expand it.
You should also add a title that says "Click to expand" so that they don't
have to know/infer that the ellipsis is an active link.
I also like being able to shrink it back... right now there isn't that much
extra det
ky the above works on
Chrome/Firefox but shows a space on IE/Safari - see:
https://stackoverflow.com/questions/5881954/html-stop-child-elements-from-inheriting-parents-title-attribute
but you might have a useful title to give it.
../Dave
On 25 November 2017 at 20:47, Richard Hipp wrote:
>
What you have seems to handle the ellipsis properly (by my definition of
properly).
But you really should use title/tooltip.
On 25 November 2017 at 21:45, Richard Hipp wrote:
> On 11/25/17, Richard Hipp wrote:
> > On 11/25/17, sky5w...@gmail.com wrote:
> >> Ok, the current behavior is cool, b
On 26 November 2017 at 16:52, Ron W wrote:
> I think there needs to be some indication that there is more information.
> From my experience, an ellipses is a very common tool for this purpose - as
> long as they are visible.
>
I agree. I really think tooltips (titles) should be used as well as t
I use symlinks *very* heavily. Almost exactly 10% of the files in my main
fossil hierarchy are actually symlinks. Fossil not supporting them would be
a huge drawback for me. Good support for symlinks and nested repositories
are 2 of the details I like best about Fossil (in addition to the obvious
f
Does it stay that size with moderate activity, or does it start growing
significantly? Does the pack format slow it down, or speed it up?
Given that the Git version only has 93% of what the Fossil repo has, I'd
say Fossil is doing quite well.
../Dave
On 27 November 2017 at 16:16, Joerg Sonnenber
I would like yesterdays with a bit of whitespace between commit comments.
Also someone liked the original because the checkin tag was in a
predictable place. If you put the tag last in the extra information it
would be predictably at the right margin.
On 27 November 2017 at 21:01, Richard Hipp
I tried to add a tag to my fossil. After looking at the documentation which
said:
I did the following:
: ~/fs/Optijava ; fs tag add -n --user-override shruthi pre-dissertation
e5b61ea041
not found: pre-dissertation
: ~/fs/Optijava ; fs help tag|less
: ~/fs/Optijava ; fs tag add -n --user-override
Can I back those out any way short of re-cloning the remote fossil?
On 16 December 2017 at 16:10, Richard Hipp wrote:
> On 12/16/17, David Mason wrote:
> > I tried to add a tag to my fossil.
>
> I didn't write the "fossil tag" command - that is contributed co
he gory details.
On 16 December 2017 at 16:52, Richard Hipp wrote:
> On 12/16/17, David Mason wrote:
> > Can I back those out any way short of re-cloning the remote fossil?
>
> You can "cancel" the old tags so that they don't have any effect. You
> should see &qu
On 16 December 2017 at 20:33, Andy Bradford
wrote:
> Thus said David Mason on Sat, 16 Dec 2017 15:36:51 -0500:
>
> > I tried to add a tag to my fossil. After looking at the documentation
> > which said:
>
> The ``fossil tag'' command is for very low-lev
Why not support --dryrun and --dry-run but only document the former? Then
scripts won't break. It's not like anyone is going to accidentally use
--dry-run to mean something else.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
h
Days since start of the release branch would seem like a good proxy -
assuming you create release branches (which seems like a good idea):
1) increasing
2) small number - you could use hours instead of days if you release
multiple versions per day
3) pretty directly mappable to a commit.
4) same on
This is very funny looks a lot like the real thing:
https://git-man-page-generator.lokaltog.net/
but it's auto-generated on the fly!
../Dave
On 14 April 2018 at 07:49, Richard Hipp wrote:
> On 4/14/18, Svyatoslav Mishyn wrote:
> > (Sat, 14 Apr 06:22) Richard Hipp:
> >> Article: https
I heartily agree with this... A flag to allow a person (including
Anonymous) to make a commit that would automatically go into a new branch
like "Patch-1" (each one incrementing the branch number) is (a) better than
emailed patches, and (b) better than pull requests. Primarily because it
puts it in
seems to be the leading excuse - other than "it's not GIT".
../Dave
On 15 June 2018 at 13:35, Richard Hipp wrote:
> On 6/15/18, David Mason wrote:
> > I heartily agree with this... A flag to allow a person (including
> > Anonymous) to make a commit that would automat
Just had a quick thought that might make the conversion to library much
easier.
If you have a relatively small API interface, each of the API functions
could do a setjmp https://en.wikipedia.org/wiki/Setjmp.h and then the fatal
error routines could longjmp back. This would give you API safety, at
I really don't understand the reticence to use setjmp/longjmp to turn all
of these short-cut exits into library return-to-API trampolines. It would
allow you to retain all the existing fossil codebase. Rewriting the code
into library form is an interesting project, but it seems like a huge
amount
ote:
> On Sun, Jun 24, 2018 at 11:19 PM David Mason wrote:
>
>> I really don't understand the reticence to use setjmp/longjmp to turn all
>> of these short-cut exits into library return-to-API trampolines. It
>>
>
> To be clear: that's my reticence, not Richar
I was thinking it would be a little more than this, but perhaps:
# define FOSSIL_EXIT(n) (api_exit_status-=n,longjmp(blabla))
would actually be enough.
And a similar setjmp-calling macro at the beginning of each API function
would be all that would be required there.
../Dave
On 25 June 2018
There is nothing wrong with a C library handling its internal processing
using setjmp/longjmp, as long as there's no C++ callbacks or any other way
that C++ code that might use throw/catch can be executed from within calls
to that library.
It's a little bit more work than just replacing the calls
It does seem a bit strange that we all sell the value of fossil partly
because it has a wiki and ticket system built in. but then we don't eat
our own dog food.
I'm no better on my personal projects... but perhaps RSS can also play a
role here. Or if one could subscribe to the email updates fo
On 27 June 2018 at 11:16, Richard Hipp wrote:
> If a feature request comes in via ticket, I can either leave the
> ticket open for some future date when I might implement the idea, or I
> can close it immediately as "not a bug". If I leave it open, then
> people become alarmed at all the open bu
Warren, this looks great! Apologies for not knowing, but where did you make
these changes?
On 28 June 2018 at 04:11, Warren Young wrote:
> On Jun 27, 2018, at 8:16 AM, Richard Hipp wrote:
> >
> > If I leave [a feature request ticket] open, then
> > people become alarmed at all the open bugs aga
Looks nice. What I meant was: what do I have to change to make it work.
Thanks ../Dave
On 28 June 2018 at 18:33, Warren Young wrote:
> On Jun 28, 2018, at 6:15 AM, David Mason wrote:
> >
> > where did you make these changes?
>
> It’s most readily seen in this repo
Great! Thanks.
On 29 June 2018 at 02:24, Warren Young wrote:
> On Jun 28, 2018, at 8:53 PM, David Mason wrote:
> >
> > Looks nice. What I meant was: what do I have to change to make it work.
>
> Clone my repository, go into Fossil UI, then navigate to Admin > Ticke
It's pretty common to put classes on tags, to use CSS to
conditionally choose different renderings by simply changing the class of
the body tag.
../Dave
On 3 July 2018 at 00:23, mario wrote:
> Mon, 2 Jul 2018 17:20:17 -0600 Warren Young :
>
> > Under what conditions would you have two differen
t 11:50, Warren Young wrote:
> On Jul 2, 2018, at 9:38 PM, David Mason wrote:
> >
> > It's pretty common to put classes on tags, to use CSS to
> conditionally choose different renderings by simply changing the class of
> the body tag.
>
> I think you’d have to writ
I like it, though the timing is pretty fast, and some slides are truncated.
On 9 July 2018 at 12:06, mario wrote:
> As followup to last month` Show time.. discussion:
>
> → http://fossilslideshow.tmp.include-once.org/
>
> (Take in mind this ain't a mockup yet; just as example.)
>
> Why oh why?
>
I use a password generator of my own design - basically takes the userid,
concatenated with a fairly long secret phrase, and then I do SHA1 and
convert it to base64, giving a password like:
Acgq75VpCWjdsJaa5abe9JeX3I (don't worry, this isn't a real password to
anything)
After Warren's comment
Hi, Just discovered fossil and it looks interesting on several fronts.
Currently using Mercurial.
The only thing that concerns me is the ticket list. There are open
Code_Defect tickets from 2009, and that doesn't give me a warm fuzzy
feeling. And after all, of your software toolkit, the part yo
OK, sounds good, but it would be great it someone who Has A Clue
(unfortunately not me at this point) could go through those old
tickets and clean them up - i.e. close them as fixed, duplicates, or
will-not-implement. Call it project hygiene - make the project look a
lot more professional.
Should
You might want to look at how mercurial-server works. You set up one
remote account that owns the master repository, but then everyone can
access e.g. ssh://h...@foo.bar/reponame but each key has a command set
up that says who it is that's accessing and then it uses the rules to
control what the p
It appears that gitolite works much like mercurial-server.
What I would expect (I haven't set up fossil yet, because I need this
functionality) is that the authorized_keys file for the fossilcm user
would have:
command="/home/fossilcm/bin/fossil gate admin" ssh-rsa ...
command="/home/fossilcm/bin
The more newbie help the better... I - for one - certainly appreciate it.
On the fossil files in or out of the project directory, I suspect most
of the cases Stephen and others have had with mangling/deleting fossil
db files could be obviated (on Linux and Mac OS X) by calling the
fossil file some
On 13 August 2013 11:39, Stephan Beal wrote:
> that (brain-dead) non-const first pointer to their fwrite() replacement
> requires a cast in all fwrite()-using code. They macro-alias fwrite() to
> FCGI_fwrite() (which is how they offer drop-in support).
Couldn't you add your own macro that include
I've been trying to track the various options, particularly from Andy,
but being new to fossil, it might be easier to simply say what I need.
All I want is for my users to say:
fossil clone ssh://remote/proj.fossil clone.fossil
or similar (without identifying any fossil user or password in t
On 13 August 2013 13:06, Stephan Beal wrote:
> Didn't think of that, actually. But the fact that fossil forks a new process
> by itself for each request eliminates the benefit of fastcgi (which is
> primarily to reduce the forks by re-using the same app instance).
But those forks (on any modern U
On 5 September 2013 17:41, David Given wrote:
> (The alternative is a 2^11 word dictionary, which means coming up with
> another 422 suitable words from somewhere, which I don't think is
> feasible. The author claims the current dictionary took 300 hours to
> compile.)
There's an 7776 common word
I would think that the downloads should be set up to work for as many
people as possible.
The Mac download says: Mac 10.5 x86 but it does not run on fully
up-to-date Snow Leopard (10.6.8) as it uses a shared library later
than that available. And all the older versions are x86_64 so don't
run on
On 9 September 2013 10:07, Warren Young wrote:
> On 9/9/2013 07:03, Richard Hipp wrote:
>> I'd like to provide universal binaries for Mac, but (alas) I
>> don't know how to do that.
>
> $ ./configure --disable-dependency-tracking \
> CFLAGS='-arch x86_64 -arch i386'
>
> You can add
On 11 September 2013 11:00, wrote:
> This worked on Windows 2008 R2 64-bit, Windows 7 32-bit, Mountain Lion 10.8.4
> 64-bit.
and Snow Leopard 10.6.8 (and it's i386 so should work everywhere)
Well done! Thanks ../Dave
___
fossil-users mailing list
f
I am really looking forward to the release that includes the proper
ssh remote repositories.
I can build it for my environment, but I am teaching a course in
January and I want the students to submit assignments using their own
repositories (and encourage them to use fossil (and SCMs in general),
On 13 December 2013 16:15, Andy Bradford
wrote:
> By the way, there is one caveat that was recently introduced that
> affects how a shared SSH account works. When cloning, the URL
> user becomes the primary fossil user in the checkout.
I was just looking for when the code in trunk wo
On 14 December 2013 03:01, Andy Bradford
wrote:
> Thus said Ron Wilson on Fri, 13 Dec 2013 21:57:22 -0500:
>
>> Since you are providing a server with Fossil repos on it, your build
>> could work the way you want it for your students to use SSH for access
>> using "stock" builds of Fossil.
>
> Th
On 14 December 2013 14:42, Andy Bradford
wrote:
> I actually made it so the new Fossil server code emulates the old client
> shell probing interaction so that the client thinks it is talking to a
> shell. This allowed for backwards compatibility.
Clever!
So, if I understand correctly, I could
I'd agree with David, here. By the time most people have "large"
repositories, they can figure out if the optimization is worth it to
them. But the default should always be safety!
../Dave
On 21 December 2013 19:47, David Given wrote:
> On 21/12/13 22:00, Richard Hipp wrote:
> [...]
>> For a l
This is a very interesting discussion.
1) It sounds like checkout, open, and update should all be part of the
command rationalization discussion as they seem to overlap. Making
them sort-of synonyms but with different default *could* work (e.g.
checkout === update -overwite, update === checkout -
Great talk! And now I'm thinking about applications of SQLite...
I added a reference to Fossil in the comments.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-user
On 7 September 2014 14:00, Stephan Beal wrote:
> It takes me less time to type such a message from the CLI than it does to
> either (A) wait on emacs (my preferred editor) to start up or (B) fight with
> vi in doing the little things my fingers do intuitively in emacs.
emacsclient ?
_
I use symlinks very heavily; I'm trying to convert all my world to
fossil, but I can't get symlinks to work.
Here's a transcript:
: Daves-MacBook-Retina-784 ; ls -l current current/cmf.html
lrwxr-xr-x 1 dmason staff 5 Sep 9 22:42 current -> f2014
-rwxr-xr-x 1 dmason staff
On 11 September 2014 01:06, Andy Bradford
wrote:
> Thus said David Mason on Thu, 11 Sep 2014 00:42:09 -0400:
>
>> : Daves-MacBook-Retina-784 ; cat .fossil-settings/allow-symlinks
>> yes
>> : Daves-MacBook-Retina-784 ; fs ci -m test
>> New_Version: 240dcb9a36ff5fde
On 11 September 2014 13:50, Andy Bradford
wrote:
> Actually, it does work. The problem isn't with the versionable setting.
> There is a bug, but its in fossil open, not the setting.
>
> After you open the fossil, delete the link (which is actually now a
> file) and then do fossil update. It
I have a server that has a working directory I want to keep current
(because it's web pages that I edit elsewhere).
I want a script to run every 5 minutes and if there is any update,
email me the update log. But I don't want email every 5 minutes that
just says everything is up to date. I can fi
I want to expose the wiki and ticket system to the public, but not
anything to do with the checkins or private wiki pages..
So I set up privileges:
anonymous chmn
nobody jr
Two problems:
1) the timeline is visible. This could expose information that we
don't want. The 'y' privilege cha
On 2 October 2014 11:02, Ron W wrote:
> On Thu, Oct 2, 2014 at 9:35 AM, David Mason wrote:
>> While I'm on fossil sync, is there a way to reset the "sync source"
>> value?
>
> I think, if you provide a URL when sync'ing, Fossil remembers that. That
&
Right, what I wanted to do was get rid of the remote-url. It turns
out that if you say:
fossil remote-utl ''
it complains that it's invalid, but now it's off, so it no longer
attempts to sync.
Thanks ../Dave
___
fossil-users mailing list
fossil-use
On 2 October 2014 15:04, Andy Goth wrote:
> Type: fossil remote-url off
Ah, much cleaner! Thanks, missed that.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-use
Ah, yes; I forgot about autosync (I'm new to actually using fossil),
but I don't think it's a flaw (see below).
On 3 October 2014 01:21, Stephan Beal wrote:
> On Thu, Oct 2, 2014 at 3:35 PM, David Mason wrote:
>> fossil update -q && fossil update 2>
1 - 100 of 160 matches
Mail list logo
