Re: [fossil-users] Two easy questions

when say nothing is hurt by it…its totally and completely safe to run rebuild…nothing will be lost? If so I will do it just in case. By the way, update worked, thanks. Silly me…I vaguely remember that now. Silly me for going so long without coding anything… I guess sync brings in the wiki

Re: [fossil-users] Two easy questions

1) no. 2) make sure all of your systems have been upgraded to compatible versions (v2) and that you run "fossil rebuild" on each after upgrading. That might not solve what you're seeing, but it's a good place to start. - stephan Sent from a mobile device, possibly from bed. Please excuse

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 7:54 PM, Steve Schow wrote: > when say nothing is hurt by it…its totally and completely safe to run > rebuild…nothing will be lost? If so I will do it just in case. > Fossil has never been known to lose data. AFAIK it's the only SCM which can make that

Re: [fossil-users] Two easy questions

On 8/15/17, Stephan Beal wrote: > Sync doesn't modify the checkout. Use update for that. > > - stephan > Sent from a mobile device,. Please excuse brevity... I am on a laptop so I can say more :-) In Fossil, your "repository" and your "checkout" are separate. The

Re: [fossil-users] Two easy questions

Related to this question, anyone have any workflow suggestions for accomplishing this aside from remembering to bump the number manually in the file before every important checkin or commit? > On Aug 15, 2017, at 11:46 AM, Stephan Beal wrote: > > 1) no. > > > 1 - Is

Re: [fossil-users] Two easy questions

On 8/15/17, Steve Schow wrote: > Related to this question, anyone have any workflow suggestions for > accomplishing this aside from remembering to bump the number manually in the > file before every important checkin or commit? Fossil is self-hosting on Fossil. The way it

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 8:09 PM, Steve Schow wrote: > well I’m hoping to have a version that is stamped into the comments of the > actual file as well. Stamping that version would change the hash. To the best of my knowledge that feature cannot be implemented with DVCS (which

[fossil-users] Two easy questions

Its been a while since I used Fossil, getting back to it, and have two quick easy questions. 1 - Is there any way to embed a substitution parameter into a source file that Fossil can replace with version info at time of checkin? (similar to RCS). 2 - I previous setup my fossil system with 4

Re: [fossil-users] Two easy questions

Sync doesn't modify the checkout. Use update for that. - stephan Sent from a mobile device, possibly from bed. Please excuse brevity, typos, and top-posting. On Aug 15, 2017 19:47, "Steve Schow" wrote: > Well slight correction to question 2. After I ran sync, if I use

Re: [fossil-users] Two easy questions

well I’m hoping to have a version that is stamped into the comments of the actual file as well. For example I have some javascripts that are used in another entirely closed environment that doesn’t have access to fossil, so it would be nice to be able to know which version of the script is

Re: [fossil-users] Two easy questions

Well slight correction to question 2. After I ran sync, if I use “fossil ui” on the local machine, the web interface there on the local remote machine does show the checkin that was made on the other master repository…., but looking at my file system where its supposed to be…its not there. >

Re: [fossil-users] Two easy questions

I did upgrade them all to 2.3, but I didn’t do rebuild. Do I need to do that? > On Aug 15, 2017, at 11:46 AM, Stephan Beal wrote: > > 1) no. > > 2) make sure all of your systems have been upgraded to compatible versions > (v2) and that you run "fossil rebuild" on each

Re: [fossil-users] Two easy questions

Rebuild is rarely needed but never hurts. Fossil will tell you if it thinks a rebuild might be required. - stephan Sent from a mobile device, possibly from bed. Please excuse brevity, typos, and top-posting. On Aug 15, 2017 19:48, "Steve Schow" wrote: > I did upgrade them

Re: [fossil-users] Two easy questions

ah… I dont’ think I had any checkouts happening at that point…well maybe I have forgotten what a checkout is. I haven't used fossil in about a year. Sounds like “pull” is what I needed to do…which update accomplished for me anyway I guess, but I need to go re-read about the checkin/checkout

Re: [fossil-users] Two easy questions

On Tue, 15 Aug 2017 19:57:34 +0200, Steve Schow wrote: Related to this question, anyone have any workflow suggestions for accomplishing this aside from remembering to bump the number manually in the file before every important checkin or commit? my workaround is roughly

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 9:50 PM, Steve Schow wrote: > right.. so what you’re saying is once a file is added, its permanently > checked out basically, and any changes you make to the file are pending a > commit. > That's... not wrong. Close enough :). You do have to commit

Re: [fossil-users] Two easy questions

On Aug 15, 2017, at 11:58 AM, Richard Hipp wrote: > > With git and hg, your repository and > checkout are more closely bound and are strictly one-to-one. Not “strictly.” Git has the git-worktree command as of 2.5 which links the current checkout to a new working directory:

Re: [fossil-users] Two easy questions

On Aug 15, 2017, at 11:41 AM, Steve Schow wrote: > > Today I tried to check something in to the master repository, but even after > going to one of the others and running fossil sync, the change doesn’t show > up there…am I forgetting something? What does “fossil set

Re: [fossil-users] Two easy questions

On Aug 15, 2017, at 3:58 PM, Steve Schow wrote: > > if each script file has its own independent version, its not part of a > greater whole per say…its just the version of that exact file..nothing > more……appearing in the source comment. My ship script doesn’t care about

Re: [fossil-users] wiki in ticket comments??

I have tried with a blank line between the paragraph and the list also, same result. yes I am making sure always that the wiki menu item is selected > On Aug 15, 2017, at 4:15 PM, Warren Young wrote: > > On Aug 15, 2017, at 4:12 PM, Steve Schow wrote:

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 9:24 PM, bch wrote: > I'm not following the process. Fossil guarantees hash fidelity - explain > differently how this would work and be coherent w/i fossil? > i'm not discounting that it could work exactly as you describe, but i would consider it a

Re: [fossil-users] Two easy questions

I’m glad to hear it only took you half an hour to write the script, but again, its way overkill to have to follow any kind of build or deployment process whatsoever for these scripts. Thanks all for the helpful feedback, I will try to find a solution outside of fossil. > On Aug 15, 2017,

[fossil-users] fossil ticket comments - wiki markup?

no matter what I have tried to add enumeration lists in my fossil tickets, the ticket comment is still coming up without any formatting. I read that in order to add an enumeration list I just have to put “#” surrounded by two spaces.. But that just ends up with a totally unformatted ticket

Re: [fossil-users] wiki in ticket comments??

On Aug 15, 2017, at 3:55 PM, Steve Schow wrote: > > no matter what I have tried to add enumeration lists in my fossil tickets, > the ticket comment is still coming up without any formatting. There are two ways I can see that happening: 1. You didn’t select Wiki from the

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 8:55 PM, Steve Schow wrote: > by the way, I don’t really use git much other then bare minimum to save > something on github, so please don’t explain anything in terms of git > concepts, I won’t understand you. > Then i misunderstood your use of "add",

Re: [fossil-users] Two easy questions

On Aug 15, 2017 11:49, "Stephan Beal" wrote: On Tue, Aug 15, 2017 at 8:47 PM, Joerg Sonnenberger wrote: > On Tue, Aug 15, 2017 at 08:18:08PM +0200, Stephan Beal wrote: > > Stamping that version would change the hash. To the best of my knowledge > > that

Re: [fossil-users] Two easy questions

On Aug 15, 2017, at 3:07 PM, Steve Schow wrote: > > yea that’s way overkill. The attached script creates versioned zip files given a Fossil-versioned file name containing the file and a manifest file called VERSION. You can therefore get the version number in the file name

Re: [fossil-users] Two easy questions

On Aug 15, 2017, at 3:50 PM, Steve Schow wrote: > > I will try to find a solution outside of fossil. The ship script gets you 95% of the way there. For example, if you absolutely positively had to have the version number embedded into the deployed JS file, you could

Re: [fossil-users] Two easy questions

Thanks Warren. I’m pretty handy with sed and awk and all the rest. I’m just trying to figure out the best way to work out an automatic workflow for having a version in the source comment. wrapper scripts around fossil that do this sort of thing might work, but see if each script file has its

Re: [fossil-users] Two easy questions

warren you are being very aggressive towards me I’m not sure why. I’ve asked for some ideas for work arounds and so far none of the work arounds are really acceptable for various reasons. No offense is intended. Relax man! > On Aug 15, 2017, at 4:06 PM, Warren Young

Re: [fossil-users] Two easy questions

yea that’s way overkill. As I said earlier, these are entirely independent scripts, they are not parts of a greater whole. Creating deployment steps for each and every one of them is not a practical solution. > On Aug 15, 2017, at 2:58 PM, Warren Young wrote: > > On Aug

Re: [fossil-users] wiki in ticket comments??

yes the wiki menu item is selected yes no blank lines are present, still getting unformatted results. for example This is some paragraph # item one # item two this results in: This is some paragraph # item one # item two > On Aug 15, 2017, at 4:02 PM, Warren Young

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 8:43 PM, Steve Schow wrote: > So one quick question…is a hash created only during commit? doesn’t > happen yet during “add” right? > The hash is calculated during the commit and includes (among many other things) the timestamp of the commit in its

Re: [fossil-users] Two easy questions

Interesting, it still works for you because you have a source file and “built” file… with scripts its sorta redunant to require a built file, but some of you are starting to convince me that I may have to create that kind of procedure, always use make on everything and only distribute what is

Re: [fossil-users] Two easy questions

well…its not for a website…javascript is used for a lot of stuff out there besides the web. Its not practical for the name of the file to have a version encoded into it. > On Aug 15, 2017, at 2:25 PM, Warren Young wrote: > > On Aug 15, 2017, at 12:09 PM, Steve Schow

Re: [fossil-users] Two easy questions

uhmmm, not once did I demand that anyone make any modifications to fossil. I asked if it can do it, and if not, what are some work arounds. > On Aug 15, 2017, at 3:55 PM, Warren Young wrote: > > On Aug 15, 2017, at 3:50 PM, Steve Schow wrote: >> >>

Re: [fossil-users] wiki in ticket comments??

On Aug 15, 2017, at 4:23 PM, Steve Schow wrote: > > I have tried with a blank line between the paragraph and the list also, same > result. yes I am making sure always that the wiki menu item is selected Here’s a freshly-created Fossil repository with one ticket, formatted as

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 08:18:08PM +0200, Stephan Beal wrote: > On Tue, Aug 15, 2017 at 8:09 PM, Steve Schow wrote: > > > well I’m hoping to have a version that is stamped into the comments of the > > actual file as well. > > > Stamping that version would change the hash. To

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 8:47 PM, Joerg Sonnenberger wrote: > On Tue, Aug 15, 2017 at 08:18:08PM +0200, Stephan Beal wrote: > > Stamping that version would change the hash. To the best of my knowledge > > that feature cannot be implemented with DVCS (which requires hashing > >

Re: [fossil-users] Two easy questions

On Aug 15, 2017, at 2:53 PM, Steve Schow wrote: > > well…its not for a website…javascript is used for a lot of stuff out there > besides the web. Its not practical for the name of the file to have a > version encoded into it. Easily solved. During the “generate deployment

Re: [fossil-users] wiki in ticket comments??

i’m getting the same result with new tickets, or adding on to tickets, makes no difference. I can see that last year when I was using fossil more actively I created some tickets with enumerated lists, but I can’t recall how I actually did it. its possibly i had to use HTML directly I vaguely

Re: [fossil-users] wiki in ticket comments??

On Aug 15, 2017, at 4:12 PM, Steve Schow wrote: > > yes the wiki menu item is selected > > yes no blank lines are present, still getting unformatted results. for > example > > This is some paragraph > # item one > # item two > > this results in: > > This is some

Re: [fossil-users] Two easy questions

Yea I wasn’t meaning to say RCS is better, or I would be using it. I’m using fossil because it is so complete and a variety of reasons is far surpasses RCS. Just saying I miss that feature and looking for a work around. That particular feature of RCS is very handy for situations where you

Re: [fossil-users] Two easy questions

by the way, I don’t really use git much other then bare minimum to save something on github, so please don’t explain anything in terms of git concepts, I won’t understand you. I used RCS and SCCS a lot in the past. In RCS, you have to explicitly checkout a file to edit it, locking it out from

Re: [fossil-users] Two easy questions

On Tue, Aug 15, 2017 at 9:10 PM, Stephan Beal wrote: > A user can ALWAYS check contents in to a fossil repo > Filesystem permissions permitting, of course. You can't commit changes to a repo opened from a CD or other read-only media. -- - stephan beal

Re: [fossil-users] Two easy questions

right.. so what you’re saying is once a file is added, its permanently checked out basically, and any changes you make to the file are pending a commit. > On Aug 15, 2017, at 1:10 PM, Stephan Beal wrote: > > Nope - that's git's way of doing it (this is why i thought

Re: [fossil-users] Two easy questions

On Aug 15, 2017, at 12:09 PM, Steve Schow wrote: > > I’m hoping to have a version that is stamped into the comments of the actual > file as well. For example I have some javascripts that are used in another > entirely closed environment that doesn’t have access to fossil, so

Re: [fossil-users] Two easy questions

On Aug 15, 2017, at 3:50 PM, Steve Schow wrote: > > its way overkill to have to follow any kind of build or deployment process > whatsoever for these scripts. One other thing: you had to have some kind of step to deploy these. If it’s just a “cp” command, build that into

[fossil-users] wiki in ticket comments??

no matter what I have tried to add enumeration lists in my fossil tickets, the ticket comment is still coming up without any formatting. I read that in order to add an enumeration list I just have to put “#” surrounded by two spaces.. But that just ends up with a totally unformatted ticket

Re: [fossil-users] wiki in ticket comments??

On Aug 15, 2017, at 4:46 PM, Steve Schow wrote: > > i’m getting the same result with new tickets, or adding on to tickets, makes > no difference. Send back the changed repository so that I (or someone else) can examine it. ___

Re: [fossil-users] Ability for user to edit the contact info?

Furthermore, the way I use Fossil, I don't want there to be such a mechanism, because I do not want users falsifying their contact information. You are welcomed to try to add the new capability, but make sure it is off by default and that some kind of new permission letter is required in order

Re: [fossil-users] wiki in ticket comments??

well figured it out.. for some reason my main repository had the following options enabled in Admin:Configuration Use HTML as wiki markup language I’m not sure why it was enabled. Turned it off and enumeration works fine now. its unfortunate, I think maybe I had that on because I have some

Re: [fossil-users] wiki in ticket comments??

On Aug 15, 2017, at 4:28 PM, Warren Young wrote: > > Here’s a freshly-created Fossil repository with one ticket, formatted as you > ask: > >https://drive.google.com/open?id=0B6JrNPgaCV7RYldEc0d6MnpXTGc I apologize to those who have tried the link since I created it: I

Re: [fossil-users] wiki in ticket comments??

On Aug 15, 2017, at 5:46 PM, Steve Schow wrote: > > well figured it out.. for some reason my main repository had the following > is it possible to have a diagram on my wiki page without that HTML option > checked? Fossil Wiki syntax accepts HTML tags. See:

Re: [fossil-users] Two easy questions

Thus said Steve Schow on Tue, 15 Aug 2017 15:50:39 -0600: > Thanks all for the helpful feedback, I will try to find a solution > outside of fossil. Whatever you end up doing, if possible please report back to the mailing list for the sake of the archive. That way if someone has the same

Re: [fossil-users] wiki in ticket comments??

hmm, I created a new repository and works fine there…very strange.. > On Aug 15, 2017, at 5:09 PM, Warren Young wrote: > > On Aug 15, 2017, at 4:46 PM, Steve Schow wrote: >> >> i’m getting the same result with new tickets, or adding on to tickets,

[fossil-users] Ability for user to edit the contact info?

I couldn't find any way for a user to edit his/her own email address (contact info), doesn't seem to be in /my page. Is there a "hidden" way? If not it would be nice to add that :) Tell me if you need me to add a ticket. Cheers. ___ fossil-users

Re: [fossil-users] Ability for user to edit the contact info?

On 8/15/17, Bohwaz wrote: > I couldn't find any way for a user to edit his/her own email address > (contact info), doesn't seem to be in /my page. > > Is there a "hidden" way? If not it would be nice to add that :) Tell me > if you need me to add a ticket. There is no such