> The problem with incremental imports is the SHA1 hash mapping between
> git and Fossil: in the pure content case (blobs) they may be the same,
> but the correspondence between git commits and manifest artifacts is not
> currently saved anywhere. I don't think it should be too much difficult
> t
On 7/15/13, Martin Gagnon wrote:
> Le 15 juil. 2013 18:21, "B Harder" a écrit :
>>
>> Is there a:
>>
>> $ fossil co initial_ci
>>
>> Command/workalike available, or am I left to:
>>
>> $ fossil timel -n | tail
>> [copy SHA1]
>> $ fossil co [paste SHA1]
>>
>> ?
>
> You can tag the initia
On Mon, Jul 15, 2013 at 03:21:54PM -0700, B Harder wrote:
> Is there a:
>
> $ fossil co initial_ci
>
> Command/workalike available, or am I left to:
>
> $ fossil timel -n | tail
> [copy SHA1]
> $ fossil co [paste SHA1]
>
> ?
>
> -bch
>
I got it..
what you want is:
fossil up ro
Le 15 juil. 2013 18:21, "B Harder" a écrit :
>
> Is there a:
>
> $ fossil co initial_ci
>
> Command/workalike available, or am I left to:
>
> $ fossil timel -n | tail
> [copy SHA1]
> $ fossil co [paste SHA1]
>
> ?
You can tag the initial commit if it's important for you. So you just hav
** s/don't want to remain pure/want to remain pure/.
On 7/15/13, B Harder wrote:
> On 7/15/13, Stephan Beal wrote:
>> On Tue, Jul 16, 2013 at 12:21 AM, B Harder wrote:
>>
>>> Is there a:
>>>
>>> $ fossil co initial_ci
>>>
>>> Command/workalike available, or am I left to:
>>>
>>> $ fossil timel
On 7/15/13, Stephan Beal wrote:
> On Tue, Jul 16, 2013 at 12:21 AM, B Harder wrote:
>
>> Is there a:
>>
>> $ fossil co initial_ci
>>
>> Command/workalike available, or am I left to:
>>
>> $ fossil timel -n | tail
>> [copy SHA1]
>> $ fossil co [paste SHA1]
>>
>
> There is a way to do it
On Tue, Jul 16, 2013 at 12:53 AM, Stephan Beal wrote:
> === 2007-07-21 ===
> 14:10:57 [dbda8d6ce9] Initial check-in of m1 sources. (user: drh tags:
> trunk)
> 14:09:59 [a28c83647d] initial empty baseline (user: drh tags: trunk)
>
PS: fossil turns 6 next week!
--
- stephan beal
http://wande
On Tue, Jul 16, 2013 at 12:21 AM, B Harder wrote:
> Is there a:
>
> $ fossil co initial_ci
>
> Command/workalike available, or am I left to:
>
> $ fossil timel -n | tail
> [copy SHA1]
> $ fossil co [paste SHA1]
>
There is a way to do it but you have to know the timeframe when the repo
Is there a:
$ fossil co initial_ci
Command/workalike available, or am I left to:
$ fossil timel -n | tail
[copy SHA1]
$ fossil co [paste SHA1]
?
-bch
--
Brad Harder
Method Logic Digital Consulting
http://twitter.com/bcharder
___
fossil-us
On Mon, Jul 15, 2013 at 3:21 PM, Sean Woods wrote:
>
>> This all works fine, with one significant exception. When I do a
>> diff operation on many files that are updated during the incremental
>> import, it appears that the entire file is "new." In other words,
>> the left hand side of the diff
On Mon, Jul 15, 2013 at 12:23 PM, Matt Welland wrote:
>
> On Mon, Jul 15, 2013 at 8:50 AM, Stephan Beal wrote:
>
>> On Mon, Jul 15, 2013 at 5:38 PM, Matt Welland wrote:
>>
>>> ...know to just try again on the occasional update fail due to a busy
>>> fossil. A more graceful fail or better yet a wa
On 2013-07-15 02:34, David Mason wrote:
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 th
On Mon, Jul 15, 2013 at 8:50 AM, Stephan Beal wrote:
> On Mon, Jul 15, 2013 at 5:38 PM, Matt Welland wrote:
>
>> ...know to just try again on the occasional update fail due to a busy
>> fossil. A more graceful fail or better yet a wait and retry would be nice
>> but recovery is as simple as up-a
On Mon, Jul 15, 2013 at 5:38 PM, Matt Welland wrote:
> ...know to just try again on the occasional update fail due to a busy
> fossil. A more graceful fail or better yet a wait and retry would be nice
> but recovery is as simple as up-arrow, enter.
>
i've been bitten by NFS-related deficiencies
I don't think NFS should be a problem. I am involved in an installation
using fossil on NFS with over 300 fossils synced between 3 sites. Some 300
users have access but I'm not sure how many are actively accessing the
repos. All fossils are accessed via NFS so collisions happen all the time.
People
> This all works fine, with one significant exception. When I do a diff
> operation on many files that are updated during the incremental import, it
> appears that the entire file is "new." In other words, the left hand side of
> the diff is blank and the right hand side is entirely green. If
On Mon, Jul 15, 2013 at 8:23 AM, Mohd Radzi Ibrahim wrote:
> After update to the latest (I think it was one month ago or so), I run
> "fossil all rebuild" while the fossil daemon is running.
>
> 1. fossil update
> 2. make; sudo make install
> 3. fossil all rebuild
>
>
I'm not sure what the "fossi
On Mon, Jul 15, 2013 at 2:08 PM, Richard Hipp wrote:
>
>
> On Mon, Jul 15, 2013 at 7:39 AM, Stephan Beal wrote:
>
>> Hi, all,
>>
>> i have just installed a fossil repo on a company-internal Linux server
>> and i am seeing a weird new error message at the top of all pages:
>>
>> error code 28: fil
On Jul 15, 2013 8:17 PM, "Richard Hipp" wrote:
>
>
>
> On Mon, Jul 15, 2013 at 8:13 AM, Mohd Radzi Ibrahim
wrote:
>>
>> I have similar issue. It was running on Ubuntu local folder. I run "all
rebuild" while the server still running. From there on I got the same
message on the web interface. How d
On Mon, Jul 15, 2013 at 8:13 AM, Mohd Radzi Ibrahim wrote:
> I have similar issue. It was running on Ubuntu local folder. I run "all
> rebuild" while the server still running. From there on I got the same
> message on the web interface. How do we fix this?
>
Can you describe how to reproduce the p
I have similar issue. It was running on Ubuntu local folder. I run "all
rebuild" while the server still running. From there on I got the same
message on the web interface. How do we fix this?
Thanks.
On Jul 15, 2013 8:09 PM, "Richard Hipp" wrote:
>
>
> On Mon, Jul 15, 2013 at 7:39 AM, Stephan Be
On Mon, Jul 15, 2013 at 7:39 AM, Stephan Beal wrote:
> Hi, all,
>
> i have just installed a fossil repo on a company-internal Linux server and
> i am seeing a weird new error message at the top of all pages:
>
> error code 28: file renamed while open: /.../bss-scripts.fsl
>
This is a warning mes
On Mon, Jul 15, 2013 at 1:37 PM, ST wrote:
> Hi,
>
> is there anything new on this?
>
Nope, but please don't take that personally. Feature requests are only
implemented as time, energy, and desire of the developer(s) allow(s).
Patches are of course welcomed :).
--
- stephan beal
http://wan
Hi, all,
i have just installed a fossil repo on a company-internal Linux server and
i am seeing a weird new error message at the top of all pages:
error code 28: file renamed while open: /.../bss-scripts.fsl
It turns out that i am on an NFS (didn't know that until just now), and i
know that NFS
Hi,
is there anything new on this?
> is it possible to mark embedded documentation pages with hierarchical
> tags, like - "fruit", "banana" and then list all pages that belong to
> the tags?
>
> If such feature is not present - may I ask to implement it?
Thank you.
ST
25 matches
Mail list logo
