Timestamps should be recorded in local timezone rather than in UTC.
1. It hurts eyes and brain to see the time in UTC and then calculate
it in local time.
2. For forensics. I'll be able to know which timezone I was while
committing that change.
And we can always calculate the UTC time anyway. And b
I personally think that "fossil open --empty" is a pretty good
strategy to keep multiple projects in the same repository.
Cheers.
- Vikrant
On 27 January 2015 at 03:57, Jim Kalafut wrote:
> I have a number of small, disparate projects that I'm moving into
> Fossil. I've noticed that "fossil im
>> But, for example fossil can provide some way to connect the stand alone
>> repositories and developers in some kind of distributed peer-to-peer network
>> and
>> to provide some interaction - I don't know - maybe some voting, messaging,
>> clone tracking, collaborative environment, pull request
> i, for one, am glad that _our_ Benevolent Dictator behaves like an empathic
> human being in public.
I second this statement. :-)
Cheers.
- Vikrant
On 14 March 2015 at 18:43, Stephan Beal wrote:
> On Sat, Mar 14, 2015 at 1:58 PM, Graeme Pietersz
> wrote:
>>
>> There is a long and interesting
The current version of Opera is 28, you should probably update your Browser.
You are using a 2 year old version which comes with Presto engine
(development of which is now discontinued by Opera), while newer
versions use Blink engine.
Cheers.
- Vikrant
On 17 March 2015 at 04:24, Tontyna wrote:
No, the authentication/authorisation is only to protect if the
repository is accessed over a protocol (http, command line etc.), if
someone has direct access to the file, they have access to _all_ of
the repository data.
To protect any file on a USB drive against theft or loss, you'll need
to eithe
Nice! Btw where can I see the build script that is fed to Launchpad's
automated build services?
Cheers.
- Vikrant
On 19 March 2015 at 17:01, Oliver Friedrich
wrote:
> I hope you don't mind that I got up an Ubuntu PPA for current fossil
> releases. This was merely a testing thing for me, to buil
Hello everyone,
I've been working on a project named "Lagerstatte", a front-end for
Fossil repositories. The browser facing part is written in Ember.js,
while server runs a Ruby on Rails application which acts as a JSON
endpoint. Access to Fossil database is provided by Stephan's excellent
libfoss
Minor grammatical correction in last email:
s/Stephan and me/Stephan and I/
On 30 March 2015 at 16:20, Vikrant Chaudhary wrote:
> Hello everyone,
>
> I've been working on a project named "Lagerstatte", a front-end for
> Fossil repositories. The browser facing
>> * Access the Fossil repositories through Git protocol (readonly).
>
> Intellectually interesting, but, for me, not a selling point as I only use
> Git when I have to.
There are lots of software and services that support Git out of the
box (e.g., CI services, Go's packages, Rust's crates, Ruby's
esults for "lagerstaette" are in German, and in
English for "lagerstatte".
* Our conclusion: "lagerstaette" when transliterating in German,
"lagerstatte" when transliterating in English.
* I'm still not 100% sure.
Maybe I should roll with "La
> That sounds like a valid $0.02 to me. JS/CSS experts: is there such tech
> that we could somehow select a vertical graph/branch indicator and have it
> highlighted somehow?
>From a quick overview of the page, an "onclick" handler on those line
and box should do the trick (in draw*() JS functio
> I'm not a German speaker, and I don't know if you care, but I would
> vote with Joerg to use "ae" rather than just "a". (Simply ignoring
> the umlaut seem just wrong - regardless of Google.) FWIW, the two
> dots in "ä" and "ö" derive historically from a small "e" placed above
> the letters "a"
> In the actual code or in string constants? If in string constants, why not
> use the ISO-8859-1 encoding? Or even Unicode? As long as your software sets
> the character set parameter in the HTTP header, this should display
> correctly.
>
> Example: Content-Type: text/html; charset=iso-8859-1
>
>
> I'm thinking about how this could be used at my workplace. On some
> projects we have shared computers called viewservers ("view" being a
> ClearCase term) on which we create our sandboxes (again, CC term).
> Switching to Fossil would mean each user getting his or her own copy of
> the full repo
>> You are probably thinking about a "shallow clone".
>
> You'll have to tell me what you mean by those words.
Here is the concept in Git: http://stackoverflow.com/q/6941889
> The impression I get is that we're both talking about the local
> repository containing things not sync'ed upstream, for
> This may be related to the scaling issue, see the discussion started by
> Richard Hipp, entitled "Fossil 2.1: Scaling".
Some great ideas by Richard and very useful feature for large
repositories (like Matt and Andy have). Though I think his intended
goals are slightly different than what I was e
> While I know very little about databases, this sounds a lot like any records
> not found in the "local" database would be read from a "remote" database.
> And any writes would be to the local database with updates to the remote
> being managed by an explicit update procedure. And this would happe
I'm sorry if this question has been raised before but I couldn't find
sufficient content on this over web.
Is it possible to convert an Apache Subversion repository into a
Fossil repository (yet)?
--
-nasa
http://vikrant.co.in/
___
fossil-users mailing
19 matches
Mail list logo
