On 21 August 2013 05:25, Donny Ward wrote:
>
> I get the same problem every once in awhile. Many times actually. I consider
> myself a heavy fossil user. My most active repository has 1087 checkins all
> made by me.
>
> I once submitted a ticket about it here:
> http://www.fossil-scm.org/xfer/tktv
On Aug 20, 2013 8:25 PM, "Donny Ward" wrote:
>
> Hey Richard,
>
> I get the same problem every once in awhile. Many times actually. I
consider myself a heavy fossil user. My most active repository has 1087
checkins all made by me.
>
> I once submitted a ticket about it here:
http://www.fossil-scm.
Hey Richard,
I get the same problem every once in awhile. Many times actually. I
consider myself a heavy fossil user. My most active repository has 1087
checkins all made by me.
I once submitted a ticket about it here:
http://www.fossil-scm.org/xfer/tktview/f7879271cf4182d2?plaintext
I have not
On Tue, Aug 20, 2013 at 10:25:05PM +0200, Stephan Beal wrote:
> On Tue, Aug 20, 2013 at 10:10 PM, Chad Perrin wrote:
>
> > Given a shared hosting account where you want to host a Fossil
> > repository, where following the directions for CGI-based Fossil hosting
> > gives you access to the web UI
Hi j.,
I'm responsible for the new and "improved" Tk diff and would like to
look into these problems. Send any screenshots and/or hate mail my way.
I'd also like to know what OS and Tcl/Tk version you're using.
j. van den hoff wrote:
however, regarding the _new_ Tk window (as of fossil versio
On Tue, Aug 20, 2013 at 10:25 PM, Stephan Beal wrote:
> # cat .htaccess
> Options +ExecCGI +Indexes
>
> IndexOptions FancyIndexing NameWidth=*
>
> # doesn't work on my hoster :( AddHandler cgi-script .html
> DirectoryIndex index.cgi index.php index.html
>
And...
# cat index.cgi
#!/path/to/fos
On Tue, Aug 20, 2013 at 10:10 PM, Chad Perrin wrote:
> Given a shared hosting account where you want to host a Fossil
> repository, where following the directions for CGI-based Fossil hosting
> gives you access to the web UI via example.com/cgi-bin/access_name, I
> would like to know what techniq
Given a shared hosting account where you want to host a Fossil
repository, where following the directions for CGI-based Fossil hosting
gives you access to the web UI via example.com/cgi-bin/access_name, I
would like to know what techniques people use to make it available via
something like one of t
On Tue, Aug 20, 2013 at 9:03 PM, John Long wrote:
> is called gpgme (gpg made easy) IIRC. I think it's not something you have
> to
> link and you should be able to tell if it's present or not.
>
i can't personally commit to it, but maybe someone who's listening can.
> My understanding is you a
Hello,
Now that I found a free Fossil hosting I can publish the changes I had
been experimenting with:
https://chiselapp.com/user/etanol/repository/fossil-better-import/timeline?r=git-better-import
What began as a way to correctly handle copies and renames, has ended
supporting delta manifests t
On Tue, Aug 20, 2013 at 08:43:36PM +0200, Stephan Beal wrote:
> On Tue, Aug 20, 2013 at 8:39 PM, John Long wrote:
>
> > If you're working on flagging PGP commits then it would be really nice to
> > say PGP in red if the signature doesn't verify or green if it does or
> > something like that. Othe
On Tue, Aug 20, 2013 at 8:39 PM, John Long wrote:
> If you're working on flagging PGP commits then it would be really nice to
> say PGP in red if the signature doesn't verify or green if it does or
> something like that. Otherwise saying "PGP" on a commit does more harm than
> good imho. Personal
On Tue, Aug 20, 2013 at 08:32:21PM +0200, Stephan Beal wrote:
> On Tue, Aug 20, 2013 at 8:07 PM, John Long wrote:
>
> > I need to go back in the archives and see where I can find an example of
> > this but in the meantime to ask the obvious, is fossil verifying the
> > signatures as part of the c
On Tue, Aug 20, 2013 at 2:32 PM, Stephan Beal wrote:
> On Tue, Aug 20, 2013 at 8:07 PM, John Long wrote:
>
>> is fossil verifying the
>> signatures as part of the commit process or does fossil simply carry the
>> data so the signature can be verified manually?
>>
>
> It simply carries them over
On Tue, Aug 20, 2013 at 8:07 PM, John Long wrote:
> I need to go back in the archives and see where I can find an example of
> this but in the meantime to ask the obvious, is fossil verifying the
> signatures as part of the commit process or does fossil simply carry the
> data so the signature ca
On Tue, 20 Aug 2013 18:41:39 +0200
Stephan Beal wrote:
> However... i don't want to move this to the trunk until i hear some
> feedback from the devs whether this is the optimal solution or whether
> something like a simple "PGP" would do.
Sure, let's hear what others can say...
Sincerely,
Gou
I need to go back in the archives and see where I can find an example of
this but in the meantime to ask the obvious, is fossil verifying the
signatures as part of the commit process or does fossil simply carry the
data so the signature can be verified manually?
On Tue, Aug 20, 2013 at 08:00:41PM
On Tue, Aug 20, 2013 at 6:25 PM, j. van den hoff
wrote:
> On Tue, 20 Aug 2013 17:59:11 +0200, Benedikt Ahrens <
> benedikt.ahr...@gmx.net> wrote:
>
> Hello,
>>
>> the fossil timeline command shows UTC time rather than observing the
>> system setting (UTC+02:00, in my case).
>> Is there anything I
On Tue, Aug 20, 2013 at 6:22 PM, j. van den hoff
wrote:
> indeed, things are moving fast with fossil ;-)
>
This year is turning out to be one of the busier ones:
http://fossil-scm.org/index.html/reports?view=byyear
and recent activity has been pretty high:
http://fossil-scm.org/index.html/repo
On Tue, Aug 20, 2013 at 6:19 PM, Gour wrote:
> Yeah, functionality is there, some cosmetic is required...link can point
> to http://some-domain/artifact/id, but the link title can be e.g. just
> *PGP-SIGNED* ?
>
i don't see a way to do that without hard-coding the link into the comment
(which wo
On Tue, 20 Aug 2013 17:59:11 +0200, Benedikt Ahrens
wrote:
Hello,
the fossil timeline command shows UTC time rather than observing the
system setting (UTC+02:00, in my case).
Is there anything I can do to change this?
you can switch off UTC (so that it uses local time) in the web interface
On Tue, 20 Aug 2013 17:31:24 +0200, Richard Hipp wrote:
On Tue, Aug 20, 2013 at 10:57 AM, j. van den hoff
wrote:
not a big deal but slightly irritating:
the tk-window opened by `diff --tk' is "editable", i..e one can modify
the
displayed diff text (w/o any real effect, of course). I don
On Tue, 20 Aug 2013 16:10:05 +0200
Stephan Beal wrote:
> Please do an update, 'make', fossil rebuild, and try again. i'm not
> terribly happy with how the link looks, but that seems to be the way
> those links are supposed to be displayed in the timeline.
Yeah, functionality is there, some cosme
Hello,
the fossil timeline command shows UTC time rather than observing the
system setting (UTC+02:00, in my case).
Is there anything I can do to change this?
fossil version is 1.26.
Thanks.
Benedikt
___
fossil-users mailing list
fossil-users@lists.fos
On Tue, Aug 20, 2013 at 5:56 PM, Benedikt Ahrens wrote:
> It works fine with 1.26.
>
:)
> BTW, is there any chance the Debian packaging could happen in a debian
> branch of the fossil development repository, i.e. that the Debian fossil
> maintainer get write access to that repo?
>
@that maint
> On Mon, Aug 5, 2013 at 10:15 PM, Richard Hipp wrote:
>
>> On Mon, Aug 5, 2013 at 3:55 PM, Benedikt Ahrens
>> wrote:
>>
>>> is not feasible in my situation.
>>>
>>
>> packages or libraries or deal with package managers. Just copy *one file*
>> into your $PATH on each machine where it matters.
On Tue, Aug 20, 2013 at 10:57 AM, j. van den hoff wrote:
> not a big deal but slightly irritating:
>
> the tk-window opened by `diff --tk' is "editable", i..e one can modify the
> displayed diff text (w/o any real effect, of course). I don't know Tk, but
> maybe there's an option to make the wind
not a big deal but slightly irritating:
the tk-window opened by `diff --tk' is "editable", i..e one can modify the
displayed diff text (w/o any real effect, of course). I don't know Tk, but
maybe there's an option to make the window readonly in order to avoid any
potential confusion (since
On Tue, Aug 20, 2013 at 4:02 PM, Gour wrote:
> On Tue, 20 Aug 2013 15:42:19 +0200
> Stephan Beal wrote:
>
> > To the raw manifest, you mean?
>
> Yes, to the one e.g. showed by Richard:
>
> http://www.fossil-scm.org/fossil/artifact/22c1ac41d4c02c44
Please do an update, 'make', fossil rebuild,
On Tue, 20 Aug 2013 15:42:19 +0200
Stephan Beal wrote:
> To the raw manifest, you mean?
Yes, to the one e.g. showed by Richard:
http://www.fossil-scm.org/fossil/artifact/22c1ac41d4c02c44
Sincerely,
Gour
--
One who is not disturbed in mind even amidst the threefold
miseries or elated when t
On Tue, Aug 20, 2013 at 3:34 PM, Gour wrote:
> It's OK, and it would be superb to e.g. have *PGP SIGNED* as hyperlink
> to the artifact?
>
To the raw manifest, you mean?
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
On Tue, 20 Aug 2013 14:58:49 +0200
Stephan Beal wrote:
> Can you please try that out, Gour?
My mistake...I mixed fossil versions for commit and ui.
It's OK, and it would be superb to e.g. have *PGP SIGNED* as hyperlink
to the artifact?
Sincerely,
Gour
--
Not by merely abstaining from work c
On Tue, Aug 20, 2013 at 9:23 AM, Gour wrote:
> On Tue, 20 Aug 2013 14:58:49 +0200
> Stephan Beal wrote:
>
> > Can you please try that out, Gour?
>
> Here is output from configure:
>
> gour@atmarama ~/t/fossil> ./configure
>
Try instead: ./configure --disable-lineedit
> Host System...x86_64
On Tue, Aug 20, 2013 at 3:23 PM, Gour wrote:
> On Tue, 20 Aug 2013 14:58:49 +0200
> Stephan Beal wrote:
>
> > Can you please try that out, Gour?
>
> Here is output from configure:
>
Do:
fossil co timeline-pgp-marker
./configure
make clean
make
./fossil rebuild
./fossil ui
and then you'll see
On Tue, 20 Aug 2013 14:58:49 +0200
Stephan Beal wrote:
> Can you please try that out, Gour?
Here is output from configure:
gour@atmarama ~/t/fossil> ./configure
Host System...x86_64-unknown-linux-gnu
Build System...x86_64-unknown-linux-gnu
C compiler... cc -g -O2
C++ compiler... c++ -g -O2
Buil
On Tue, Aug 20, 2013 at 2:11 PM, Stephan Beal wrote:
> i've just written down a TODO to add this info to the timeline if it's not
> terribly problematic. The main problem is that the timeline doesn't have
> that level of data. Ah, but it could - we could still see the PGP key in
> the crosslink p
On Tue, Aug 20, 2013 at 2:05 PM, Gour wrote:
> Iow, I'd like an easy way to check whether the commit is signed or not,
> possibly close to the 'SHA1 Hash:' label or something.
>
i recently some samething similar in the JimTCL timeline, where each commit
has a "signed off by...", but i don't know
On Tue, Aug 20, 2013 at 8:05 AM, Gour wrote:
>
> Iow, I'd like an easy way to check whether the commit is signed or not,
> possibly close to the 'SHA1 Hash:' label or something.
>
> I'm also pretty sure that something like that was available or am I
> dreaming...
>
I think you dreamed it. I don
On Tue, 20 Aug 2013 07:47:42 -0400
Richard Hipp wrote:
> The PGP signature is recorded in the repository. (See, for example
> the PGP signature on an early check-in to Fossil itself at
> http://www.fossil-scm.org/fossil/artifact/22c1ac41d4c02c44).
OK.
> However, I have never added any logic in
On Tue, Aug 20, 2013 at 7:42 AM, Gour wrote:
> Hello,
>
> I've converted (mostly from Git, but as well as from darcs & btr) *all*
> my repost to Fossil in order to exclusively use it and test it
> thoroughly.
>
> Now I experience some (strange) problem that I can't see GPG signatures
> in my comm
Hello,
I've converted (mostly from Git, but as well as from darcs & btr) *all*
my repost to Fossil in order to exclusively use it and test it
thoroughly.
Now I experience some (strange) problem that I can't see GPG signatures
in my commits.
During commit I see the following:
You need a passphra
41 matches
Mail list logo
