Ok, obscured my email, but that cat has been out of the bag for years :(
On Sat, Aug 11, 2018 at 2:06 PM, wrote:
> Doh! Didn't know you could submit a dummy email.
> Even though mail is deprecated, are we still able to change settings?
>
>
Doh! Didn't know you could submit a dummy email.
Even though mail is deprecated, are we still able to change settings?
http://lists.fossil-scm.org:8080/cgi-bin/mailman/options/fossil-users
I asked for my password and no reply?
On Sat, Aug 11, 2018 at 2:01 PM, Andy Bradford <
Sorry, I re-checked my spam folder and the last one arrived Jul-24.
On Fri, Aug 10, 2018 at 1:35 PM, wrote:
> Whoa, I still receive spam from this mail list. :(
> While hard to track, I cannot say the same with the forums I use.
> Of course, forums can be hacked and emails exposed, but that is
Whoa, I still receive spam from this mail list. :(
While hard to track, I cannot say the same with the forums I use.
Of course, forums can be hacked and emails exposed, but that is rare and
targeting richer bounty.
The fossil forum is a click away. If you resist, then write a crawler to
retrieve
Hmmm, that sounds like TortoiseFossil?
I would deploy that if available. :)
On Mon, Aug 6, 2018 at 9:42 PM, Gilles wrote:
> On 07/08/2018 03:21, Ron W wrote:
>
> I never tried Sharp Fossil, but Fuel was a very clunky GUI. I think
> non-programmers would be unwilling to put up with it.
>
> As a
My repo's were built prior to the unversioned feature, so I have not used
this yet. And there is no benefit to migrating my candidate files to
unversioned since their history will remain in the repo without complex
shunning.
But now I am confused by this thread?
If/When I add unversioned files,
Can unversioned files respect their original paths when added?
I have several locations for bitmaps, icons, pdf's, etc.
They do not necessarily reside in an isolated folder.
Thanks for the new Fossil features!
On Tue, Jun 26, 2018 at 11:31 AM, Richard Hipp wrote:
> My thought was to provide
Yes, plain text please since hyperlinks will point to richer content.
On Fri, Jun 22, 2018 at 10:46 AM, Marcelo wrote:
> El vie., 22 jun. 2018 a las 11:09, jungle Boogie ()
> escribió:
>
>>
>> I'd rather have emails delivered in plain text, bypassing
>> html/markdown but that's just my
Ha! I can see there are strong opposing opinions for mail vs forum.
I find forums more neatly packaged.
Mailing lists are not easily browsed or searched for relevant terms.
Some run on mail topics are a pain to find the nugget of information
desired.
Forum responses can have votes or kudos
Nice, that should be mentioned in the download page.
Since we don't have checksums, the filesize should be known.
On Sat, Feb 17, 2018 at 1:08 PM, Richard Hipp wrote:
> On 2/17/18, sky5w...@gmail.com wrote:
> > I built the latest Fossil [01984] using
I built the latest Fossil [01984] using ~\Fossil-01984ee0\win\buildmsvc.bat
and it creates a 2.92MB exe.
The v25 download exe when unzipped = 5.08MB?
Are there different compile settings in the download file to make such a
larger exe?
___
fossil-users
I love WinMerge and was unable to trigger the diff from fossil(many
versions ago) as you suggest?
Can you describe how WinMerge is installed and fossil settings that worked
for you?
For now, I cut and paste, which is a drag.
Thanks!
On Tue, Feb 13, 2018 at 1:11 PM, Ron W
Ardoise is looking very nice. :)
Fix the Tickets 'whiteout' and it should be the default!
On Thu, Jan 11, 2018 at 6:10 PM, Antoine Chavasse
wrote:
> I have commited a new version in the ardoise skin branch where I have
> reskinned the ticket view, which fixes the overly
Yeah, could be old guy eyes and smallish font. But, it is low strain
overall.
On Sun, Jan 7, 2018 at 5:28 PM, Jacob MacDonald wrote:
> Interesting, I don't notice any contrast issues on my monitor. The font in
> diffs could be a little bigger but the black on green being a
Very nice Timeline, but super dark when browsing diff's?
The green background needs to be lighter or the font needs brightening.
On Sun, Jan 7, 2018 at 4:51 PM, Jacob MacDonald wrote:
> Wow that's a slick skin. Antoine, if you're on the list, top notch work.
> Can't wait to
Big thanks to Zakero for highlighting subtle CSS/html components necessary
to achieve my desired Compact view.
With the following changes, I now prefer Compact view over Modern.
/* CSS */
span.timelineCompactComment {
display: block;/*Necessary for margin-top to work.*/
Is this leading and trailing newline in 'timeline[Modern|Compact]Comment'
intentional or bug?
Is it necessary to create padding for the borders?
If so, why can't borders be applied with CSS?
I'm trying to shrink my Timeline text but no idea what CSS strips contents
of object?
What I see...
"
Ok, using Google Chrome Version 65, I never see CheckBox anywhere within
trunk of:
http://fossil-scm.org/index.html/timeline.
"Johan"
Leaf check-in: a6c5a462 user: drh tags: trunk
When you select that element, you should see, in one of the "Developer's
Tools" frames, the definition for the
Thanks for the holiday reading material Johan!
This helps a lot. Every time I dabble in HTML, it only makes it to short
term memory. :(
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Came back to this after dinner.
The introduction of new Timeline classes(Modern,Compact,Verbose,Columnar)
means there is no catch-all for timelineComment.
So, I cut and paste in the CSS for each possible case.
/* Enable timeline comments to respect linefeeds. */
span.timelineModernComment {
Ok, I clicked and clacked with the Publish button and I am getting changes.
Before, I could edit my CSS and the page would reflect the changes
immediately.
I now think I have a corrupt CSS, since I lost my menus and header/footer.
I'll edit the default CSS and re-insert the 'white-space: pre;'
I just compiled fossil version 2.5 [a6c5a4620a] 2017-12-18 02:06:40 UTC
under Windows 10 and nothing(every view option + CSS + Timeline option) I
try shows my commit comment[CR][LF]'s.
Any ideas?
My check-in comments are intentionally multi-line. Stripping the newlines
renders my timeline as
Wow, you are fast. Back to 1 pair ().
On Dec 11, 2017 8:13 PM, "Richard Hipp" wrote:
> On 12/11/17, sky5w...@gmail.com wrote:
> > Compact view now has double ((parentheses)) ??
>
> Did you press "Reload"? Can you send me a link to the page you are
>
Compact view now has double ((parentheses)) ??
On Dec 11, 2017 7:03 PM, "Richard Hipp" wrote:
> A new version of Fossil is up with some minor UI tweaks:
>
> (1) No more box around comments in the Modern and Columnar views.
> Instead, the background color is a light gray.
>
>
I agree. Why does the [brief-hash] need to be a hyperlink and bracketed
when the Timeline time stamp has the same link?
On Tue, Dec 5, 2017 at 9:30 AM, Reimer Behrends wrote:
> Richard Hipp wrote:
>
>> Which is better?
>>
>>A: https://www.fossil-scm.org/a/timeline
>>
Focusing on the Compact view:
Is there any chance to limit the click action to just the ellipses?
And to revert, click on the added content, Ex. "check-in:" or "user:".
As others mentioned, it is annoying when selecting text from the comments
to have the background action.
On Wed, Nov 29, 2017 at
I will try smallest scaling of the ellipsis, if it really must remain...
And I can live with .timelineEllipsis { display: 'none'; }, since the
Advanced button will override if I want extra info.
Thanks for the options.
On Sat, Nov 25, 2017 at 9:52 PM, David Mason wrote:
>
Ok, the current behavior is cool, but renders the ellipses superfluous.
Clicking anywhere in a line expands/contracts the info.
Any chance to drop the many many ⋯'s after all my comments?
On Sat, Nov 25, 2017 at 8:47 PM, Richard Hipp wrote:
> On 11/25/17, David Mason
Man, are those ellipses absolutely necessary?
(So close with the previous uncluttered timeline.)
Is it possible to make the 1st word/sentence of the checkin comment a
hyperlink to the extra info?
On Sat, Nov 25, 2017 at 5:51 PM, Marc Simpson wrote:
> One other (potential)
"(2) Decluttered should be the default."
I agree clutter should not be default?
I would drop that term altogether.
On Sat, Nov 25, 2017 at 8:47 AM, Richard Hipp wrote:
> In the latest code on https://www.fossil-scm.org/fossil/timeline and
> at https://sqlite.org/srcx/timeline
Wow, #5 is super clean and easy on the eyes!
And #12 is interesting if I can see it with Per-Item Time Format = (off)?
Thanks for the changes!
On Fri, Nov 24, 2017 at 7:12 PM, Richard Hipp wrote:
> On 11/24/17, Zakero wrote:
> >
> > tldr; This new change of
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 similar "quiet" setting for the Timeline like *Per-Item Time
Format = (off) *to conserve space?
My commits prepend a simple timestamp in the comment and
Only these items:
*Search Check-in Comments*
*Search Documents*
*Search Tickets*
*Search Wiki*
*Search Tech Notes*
On Sat, Nov 18, 2017 at 12:02 PM, Richard Hipp wrote:
> On 11/18/17, sky5w...@gmail.com wrote:
> > Confirmed on Windows 10 Pro, fossil
Confirmed on Windows 10 Pro, fossil version 2.4 [a0001dcf57] 2017-11-03
09:29:29 UTC.
My crash happened in a Timeline search for '.', not that I would ever do
that. :)
On Fri, Nov 17, 2017 at 6:04 PM, Tony Papadimitriou wrote:
> I forgot to mention this is a on Windows machine
Great, I'll give that a try.
On Wed, May 10, 2017 at 4:17 PM, Richard Hipp wrote:
> On 5/10/17, sky5w...@gmail.com wrote:
> > Cool,
> > Does this behave identically if I have:
> > http://localhost:8082/setup_settings
> > [±] autosync //<-- ON or OFF?
Cool,
Does this behave identically if I have:
http://localhost:8082/setup_settings
[±] autosync //<-- ON or OFF?
Thanks.
On Wed, May 10, 2017 at 9:34 AM, David Mason wrote:
> Perfect! I knew it would be easy.
>
> Thanks
>
> On 10 May 2017 at 07:04, Richard Hipp
the.tick - "Where and how would I use the above?"
Browse a fossil ui of your repo and edit the skin - CSS page:
http://localhost:8082/setup_skinedit?w=0
On Wed, Mar 29, 2017 at 5:18 PM, The Tick wrote:
> On 3/29/2017 4:03 PM, sky5w...@gmail.com wrote:
>
>> Doh! It was my CSS.
Doh! It was my CSS. I was using a test repo without my modified CSS. Now it
works.
I think this is the 2nd time I tripped on this. :(
// from CSS //
/* THIS DOES NOT WORK - Enable Check-in comments to respect linefeeds. */
span.checkinComment {
font-family: Consolas;
white-space: pre;
}
/*
Yes, change your text files to UTF-8 with BOM(unsure without BOM) and
Fossil respects °, ±, ©, ®, special characters.
Side note:
I have all Timeline Display Preferences unchecked and my v2.1 Timeline does
not respect new lines in my check-in comment?
v1.37 showed newlines in the Timeline for
Thanks for the detailed replies.
I will make the leap to v2.1 shortly.
Thanks for Fossils-ha!
On Thu, Mar 9, 2017 at 7:02 PM, Warren Young wrote:
> On Mar 9, 2017, at 3:11 PM, sky5w...@gmail.com wrote:
> >
> > I am asking since I would prefer to create new repo's with sha3
Confused a bit reading this...will Fossil 2.1 default to sha3 or sha1
hardened?http://www.fossil-scm.org/index.html/doc/trunk/www/hashpolicy.wiki"A
Pure SHA3 FutureAt some point in the future, years from now, after
everybody has finally upgraded to Fossil 2.0 or later, the default hash
policy will
Yeah, I'm just pointing out a change from v2.0 and down.
I think it's the 'underlining' effect that is taking extra room as the menu
collapses with zoom. Some earlier versions don't even attempt menu wrap and
make use of horizontal scrollbar. No biggie as I may be confusing stock
skins with
I am using Chrome and menu works when extending width of browser.
But, the scrunch appears with no scrollbar. My zoom is 175%.
https://www.reddit.com/r/fossil/comments/5y1ngw/fossil_21f32c36e58a_menu_scrunch_on_chrome/?ref=share_source=link
Thanks for Fossil.
Sorry for double post, I got spammed between reply and lost track of what I
deleted. :(
On Wed, Mar 1, 2017 at 11:14 AM, wrote:
> Cool!
> More 2.0+ requests...
> 1. 'Prune' repo to deliver a branch or whatever as a new repo.
>Ideally, history preserved from point of
Cool!
More 2.0+ requests...
1. 'Prune' repo to deliver a branch or whatever as a new repo.
Ideally, history preserved from point of prune forward.
2. Unversioned files supported with check in/out.
Current approach is confusing(that may be intentional?).
3. Fossil 2.0+ delivered as dll.
I
All sha's aside:
1. 'Prune' repo to deliver a branch or whatever as a new repo.
Ideally, history preserved from point of prune forward.
2. Unversioned files supported with check in/out.
Current approach is confusing(that may be intentional?).
3. Fossil 2.0+ delivered as dll.
I use the exe
Thanks, I'll give it a try. :)
On Tue, Feb 21, 2017 at 4:58 AM, Jan Nijtmans
wrote:
> 2017-02-20 16:42 GMT+01:00 Richard Hipp:
> > On 2/20/17, sky5w...@gmail.com wrote:
> >> Any chance to get the Windows binary as x64 also?
>
> You can find my win64
Ah, I see it is somewhat quirky:
https://wiki.openssl.org/index.php/Compilation_and_Installation#W64
Thanks for explaining the Windows x64 gap.
On Mon, Feb 20, 2017 at 10:42 AM, Richard Hipp wrote:
> On 2/20/17, sky5w...@gmail.com wrote:
> > Any chance to
Any chance to get the Windows binary as x64 also?
Thanks for Fossil.
On Mon, Feb 20, 2017 at 9:58 AM, Roy Keene wrote:
> I'd vote for x86_64 or amd64 (or even EM64T), but not "x64" (which is
> gibberish).
>
> On Mon, 20 Feb 2017, Richard Hipp wrote:
>
> On 2/20/17, Emil
+1...much public outcry...
On Fri, Feb 3, 2017 at 3:52 PM, john lunzer wrote:
> fossil unversioned is a welcome feature as it allows me to put large
> binary test files in my repo without my .fossil file exploding in size
> every time the test files change.
>
> However, it is
I do not use sync.
I use automation to pull/push/merge/commit.
I want to use unversioned for dependency files like png,dll,exe,etc.
I prefer the coder to decide unversioned winners and not the file modified
time deciding which is kept.
So, I need some clarification on 'unversioned'?
Push to
Can confirm with gmail. Every post now has multiple spam replies.
Fossil has been discovered!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Cool.
How does 'fossil purge obliterate' differ from 'fossil shun'?
Is shun obsoleted or superseded by purge now?
Can I achieve the obliteration entirely from the cmd line?
Thanks!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
This is a welcome addition to house nuisance files like bitmaps, icons, etc.
But, I am confused by the in-out nomenclature?
Push to remote: fossil unversioned sync
Pull from remote: fossil unversioned revert
Checkout unv files: fossil unversioned export FILE //1 at a time?
If we have the
Yahoo!
Fossil v1.36[2dec4bdfcb] fixed the problem!
Compiled with VS2013 Express.
Wow, that was weird and confusing. So glad to have unified timeline back.
Thanks for Fossil!
On Wed, Jul 20, 2016 at 10:37 PM, wrote:
> Curious, I was not familiar with /bloblist URL?
> I found
Curious, I was not familiar with /bloblist URL?
I found it in the sitemap as 'List Of Artifacts'.
But it does show all 4414 entries with valid events:
ticket/wiki/filename/commit.
On Wed, Jul 20, 2016 at 10:11 PM, Richard Hipp wrote:
> On 7/20/16, sky5w...@gmail.com
Unfortunately, same results:
c:\myrepo>fossil rebuild myrepo.fossil
100.0% complete...
c:\myrepo>fossil test-integrity myrepo.fossil
4414 non-phantom blobs (out of 4414 total) checked: 0 errors
low-level database integrity-check: ok
I'll try compiling latest code.
On Wed, Jul 20, 2016 at
Thanks for checking. I am confident we have the tip after merging from
multiple user commits. But, it is certainly confusing to confirm this
visually.
http://www.fossil-scm.org/index.html/info/a78e51185326b91f
Edited Comment: Partially revert [f73411025e8ebec7]
I've noticed weird multi-line timelines with v1.35.
Is this a bug or is it the skin run amok?
This repo has only trunk and 1 very old branch.
https://www.reddit.com/r/fossil/comments/4tti7k/fossil_v1353aa86af6aa_is_this_multiline_timeline/
Thanks for Fossil!
If a built-in forum existed(yay), would users be allowed to upload images
to support their posts/queries/tickets? And if so, could those attachments
be treated less strictly regarding shunning? Deleting occasional
spammer/bot entries will be required.
On Tue, Jun 28, 2016 at 9:40 AM, Warren Young
Fossil is a gem and should not be dismissed or ignored simply because the
masses choose git. In fact, I often find the most elegant solutions in the
extremes.
On Thu, May 19, 2016 at 5:29 PM, Richie Adler wrote:
> > Not sure it's fair to include my quote when I've never
Nice, I just recovered 50% file size using:
fossil rebuild --compress-only
I had only ever used fossil rebuild and vacuum's?
Thanks for heads up.
On Fri, Nov 27, 2015 at 5:11 PM, Warren Young wrote:
> On Nov 27, 2015, at 3:06 PM, Richard Hipp wrote:
> >
> >
Maybe a dumb question, but can search be expanded to repo files? Maybe just
the tip? Is it a speed issue or too many results to process?
On Tue, Nov 10, 2015 at 9:32 PM, jungle Boogie
wrote:
> Sent from my iPhone 7.1
> On Nov 10, 2015 5:04 PM, "Steve Stefanovich"
m.org/fossil/artifact/10cb5eb292?ln=40-43
> >
> > I guess sky5walk wants that to allow through any characters other than
> 0x00
>
> My guess is that the code in doc.c was written when the function
> looks_like_binary() didn't exist yet. Should be fixed now:
> <http
Hi,
I am also trapped with this binary file detection for the egregious use of
ascii characters 2 and 6 in my code. :(
;// ascii2+sometexthere+ascii6
;//sometexthere;<-- pasting here does not show the prefix and suffix
ascii characters.
I cannot see diff's or my source code now in fossil
No, I just deleted ascii characters 2 and 6 from the file and Fossil now
shows the file as text. I will have to build this ascii string in code
instead of pasting from hex editor. But, it would be cool to set a range of
acceptable ascii characters = text. Ex. ascii 1-127 = text.
On Thu, Nov 5,
No, saving the file to utf-8 + BOM did not prompt Fossil to trigger text.
And "decent" is a relative term.
;// Temp Tol ±°C ;<-- Ansi display :)
;// Temp Tol [xB1][xB0]C ;<-- UTF-8+BOM display :(
On Thu, Nov 5, 2015 at 5:43 PM, wrote:
> Thanks for looking at this.
>
Haha, it would be quite a mess if $ and @ triggered binary.
I see no reason to kick the file to binary if the ascii code < 128?
On Thu, Nov 5, 2015 at 3:46 PM, wrote:
> No difference besides num bytes with or without the embedded Ascii
> characters 2 and 6.
> I add this 1
Yes yes, I am painfully aware of the BOM and the encoding steps.
Notepad++ has a simple menu click for this.
Despite all combinations, Fossil considers the file binary.
On Thu, Nov 5, 2015 at 6:33 PM, Warren Young wrote:
> On Nov 5, 2015, at 3:54 PM, sky5w...@gmail.com wrote:
, I do not want to use escape char's.
> > Is there any chance or setting to let Fossil v134 detection logic use
> > extended ascii character range?
>
> Background for the list: sky5walk sent me a sample file that
> contained his two control characters.
>
> What I did: I
Well, I have a workaround(no pasted literal strings). I just didn't realize
Ascii characters within 1-255 could trigger binary?
Maybe a fast histogram, and a count of << 1 or 2% for these ascii
characters allows text. Or let the user define the valid range.
By the way, Notepad, Notepad++, Visual
No difference besides num bytes with or without the embedded Ascii
characters 2 and 6.
I add this 1 line to my file and it triggers binary?!
[Asc2]+"123"+[Asc6][CR+LF]
c:\tryfossil>fossil test-looks-like-utf myfile.txt
File "myfile.txt" has 121343 bytes.
Starts with UTF-8 BOM: no
Starts with
"
Even with fossil, I am having trouble justifying why the hassle is worth
the effort.
"
Sorry, but the alternatives
(I have a Halloween shudder at the thought)
are way more effort in the long run.
I agree, merging is difficult when there are conflicts. But, Fossil and
others show your
Cool, I've often wanted this feature.
fossil diff --whatif
On Fri, Sep 11, 2015 at 10:11 AM, Richard Hipp wrote:
> On 9/11/15, Stephan Beal wrote:
> > On Fri, Sep 11, 2015 at 1:22 PM, Richard Hipp wrote:
> >
> >> I'm not sure "--undo"
Nice.
Is it possible to trim the results to only a specific file using a raw SQL
query or TH1?
Or is it quicker to just parse fossil test-whatis-all artifacts.txt
output?
Can I enter multiple artifacts(comma or space delimited) in the shun ui or
only 1 at a time?
Thanks
On Mon, Aug 17, 2015 at
I read the search feature is in a trial stage.
Can it be expanded to search in actual source files?
Now using the browser and only per file. Or of course in an external tool
in my checkout folder.
Thanks for Fossil.
___
fossil-users mailing list
The repo still grows and grows with every commit of a binary file. I don't
fully understand this definition?
binary-glob -- The VALUE is a comma or newline-separated list of (versionable)
GLOB patterns that should be treated as binary files for committing and
merging purposes. Example: *.jpg
Ok??? Kinda annoying since I clicked all 4 to see which is more relevant
only to see they are identical. Not sure why this is a preferred output? If
the auto-generate stores to a map with the link as a key, then only 1
identical key will survive. Otherwise, it requires a multi-pass cleanup.
On
This link is referenced 4 times:
http://www.fossil-scm.org/index.html/doc/trunk/www/shunning.wiki
Here:
http://www.fossil-scm.org/index.html/doc/trunk/www/permutedindex.html
Content From Fossil — Shunning: Deleting
Deleting Content From Fossil — Shunning:
From Fossil — Shunning: Deleting Content
In light of the shenanigans at sourceforge, would you consider hosting
elsewhere?
On Fri, Jun 12, 2015 at 8:09 AM, Jan Nijtmans jan.nijtm...@gmail.com
wrote:
2015-05-25 11:34 GMT+02:00 Jan Nijtmans:
For anyone interested, I built fossil 1.33 especially
for win64, it's available here:
Thanks for explaining this new feature. v1.33 showed a months old forgotten
commit and it was easy to merge and clean up. Wasn't sure how merging such
old changes would go.
Thanks for Fossil!
On Fri, May 29, 2015 at 10:24 PM, Doug Franklin nutdriverle...@comcast.net
wrote:
On 2015-05-29 19:19,
Yes, I asked about this in another thread. Can we use TH1 to color the
Timeline entries per User?
On Wed, May 27, 2015 at 1:30 PM, Ron W ronw.m...@gmail.com wrote:
On Wed, May 27, 2015 at 7:25 AM, Richard Hipp d...@sqlite.org wrote:
Fossil provides capabilities that make
it trival for the
How can I dynamically set the commit color by user using th1 in the CSS?
Thanks for fossil.
On Sat, May 9, 2015 at 10:22 AM, Kai Lauterbach kla...@web.de wrote:
Hi,
i tried to set the color of a branch as it is described here:
http://fossil-scm.org/xfer/help/commit
But it does not work
The repo is an open SQLite db. You can browse it easily with any 3rd party
SQLite viewer/editor or your own code. The passwords are hashed but
available. As are the user settings. So, someone could edit the user guest
cap to 'as' and do whatever. Better to encrypt the repo when in transit.
On
Thanks!
That worked but why not with other globals? Are they not available with the
default fossil.exe?
I initially tried this TH1 in the CSS but it failed and assumed it was not
allowed?
/* This fails */
th1
if { [ string last c $project_name ] == [ string length $project_name ]
- 1 } {
Hi,
All the skinning going on recently got me interested in tweaking my repo
appearance. Not being html/css savvy in the least, I am stumped how to
trick the CSS to use a variable background color if remote or localhost? Or
I could key on the repo name if I append a 'c' to my clones.
I understand
Richard Hipp wrote I keep most of my Fossil repos in a common directory:
~/www/repos. I currently have 64 of them sitting there.
What are you holding out on us?!
1. sqlite
2. sqlite - super awesome next
3. fossil
4. tcl editor - nsa proof
5. hal 2.0 - AI that scares Gates, Hawking and Musk
6. ..
Yes, always interesting to hear from Dr Hipp.
1. I had not considered fossil all push/pull.
2. I was hoping for a followup question to:
Fossil does not perform well with very large repo's or histories 15
years.
How is the performance hit quantified? 1day or 1hour / 1GB repo / commit?
My early experience with Fossil and autosync ON was not intuitive and I
may have experienced Dr Hipp's scenario. In my case, slow remote repo's. I
decided on a granular approach automated by my own code.
autosync OFF
Start{
fossil status ...
...review uncommitted local changes and fossil commit
Repo backups saved me in this scenario. A developer did a fossil add *.* by
mistake and committed. Well, that bloated our repo size tenfold. We knew
quickly because push/pulls were taking too long. A query to this mailing
list mentioned shun's and rebuilds, but I had already made some poor hacks
Interesting, but I am unsuccessful attempting to read any of what you post?
Can you provide a url directly to 'fx shun add' documentation?
Or do I have to install this to become Armed Dangerous? :)
On Fri, Sep 5, 2014 at 4:39 PM, Andreas Kupries andre...@activestate.com
wrote:
On Fri, Sep 5,
Well said and yes, Fossil is a non-tedious, benevolent lifesaver. My
reservation being scalability of large repo support. While I am unaffected,
those professionals charged with release and maintenance of large code
bases look past Fossil and its SQLite core.
Questions:
Will Fossil ever seek to
While disabling checksums helps with speed
http://www.fossil-scm.org/index.html/help?cmd=settings
It does not help with redundant binary images in the repo.
For that, you have to shun and rebuild.
If you could flag a file as Keep latest only, that would be less
painless. I don't mind the artifact
(2) Fossil's purpose is to be able to recreate historical versions of the
project - exactly. It cannot do that if historical images have been
deleted.
I understand the purity intended, but continue to be frustrated by it. :) I
merely seek an automated way within Fossil to manage garbage.
Took time to reply, cause I had to clean the coffee I spit up!
A released application should be considered stable and a conservative view
would say its libs should not contain alphas or betas.
The ease of compiling a bleeding edge Fossil.exe is already in place for
those wishing to gain the latest
A while back when considering Fossil, I read that 'any' database could have
been chosen in its design. This thread seems to contradict Fossil's
published design theme?
http://www.fossil-scm.org/fossil/doc/tip/www/theory1.wiki
Thoughts On The Design Of The Fossil DVCS:
We claim that Fossil is not
I am curious what is stored in the repo for each new commit that includes a
tiny change to a binary file.
Whether a dll or an image file, is fossil storing each binary file
compressed, uncompressed or some sort of delta?
Over time(6mo's to 1yr), I would like to reduce my repo size by purging
Ah, is there a way to quantify the binary delta?
If I have a 1MB binary file and commit a 1 byte change, what is the size of
the computed binary delta?
You are correct of course, but I tend not to extend the spirit of fossil to
binary files and images. It is their existence and not legacy that is
Thanks. I didn't know how binary was handled given the Timeline diff
response = cannot compute difference between binary files.
I think it would be cool if instead fossil listed some of the metrics used
or determined in the binary delta operation.
Thanks for Fossil!
On Sun, Dec 22, 2013 at 2:51
Really, I am only implying some minimal file statistic like 'DeltaSize(%)'
or somesuch to show the user it is in fact compared internally. The current
message contradicts what is in fact happening. Maybe change that message to
Cannot visually display binary diffs. DeltaSize(%) = -10.
On Sun, Dec
1 - 100 of 191 matches
Mail list logo