On Wed, Aug 6, 2014 at 1:29 AM, Warren Young war...@etr-usa.com wrote:
That has more to do with contemporaneity. When you talk about Linux 3.x,
you also necessarily imply recent versions of glibc and such, which is the
true dependency.
+1
I seriously doubt Fossil actually makes any
Or you could ask me, since I wrote autosetup :-)
I appreciate your assistance and responsiveness.
glob.tcl is bundled up in the jimsh0 executable, but you can find it because
the source code is there - autosetup/jimsh0.c
Some part of the autosetup/configure process is failing because of
Hi,
The idea of just clicking on 2 revisions in the timeline to get a diff is
very convenient, but I would like to suggest a small improvement: No matter
what order I click the boxes in, it should display the diff from the older
to the newer. To me it just makes more sense, since that is what I
On Thu, Aug 7, 2014 at 10:59 AM, Baruch Burstein bmburst...@gmail.com
wrote:
Hi,
The idea of just clicking on 2 revisions in the timeline to get a diff is
very convenient, but I would like to suggest a small improvement: No matter
what order I click the boxes in, it should display the diff
Andy Bradford wrote:
Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -:
Since I wasn't transmitting any sensitive data anyway, I answered yes,
and then got:
Error: not authorized to write
Is there something wrong with the way I'm trying to authenticate?
I see you used -B for
On 8/6/2014 21:00, Andy Bradford wrote:
Thus said B Harder on Wed, 06 Aug 2014 10:41:47 -0700:
Do we have fine-grained control over pulling only specifically rooted
branches?
No, but you can certainly clone the developers clone and inspect his
changes before pulling into your clone
Andy Bradford wrote:
Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -:
fossil push https://chiselapp.com/user/uname/repository/reponame -B
'uname:passwd'
By the way, if chiselapp does support HTTP_AUTH, then you might simply
need to enable REMOTE_USER support in your
On 8/7/2014 01:26, Stephan Beal wrote:
i'm pretty certain (not 100%) that that's it, but i know we don't use
any Linux-specific calls which might depend on a newer glibc version,
After I posted that, I went out and looked for a list of Linux syscalls
that included the point where they were
I have set up a fossil-wiki for my own use.
I look at the wiki-editing page and I see controls for some formatting
features; fonts, font-size, bolding, indentation, bullets,... These
formatting features would be useful to me. However, every time I try to
use the formatting features, nothing
On 8/7/2014 14:20, Hajas, Wayne wrote:
every time I try to
use the formatting features, nothing happens.
Wild guess: you're using a fairly recent version of IE on Windows.
You're probably running into Microsoft's brain-dead choice to run all
intranet sites in compatibility mode by default.
On 8/7/2014 14:51, Warren Young wrote:
On 8/7/2014 14:20, Hajas, Wayne wrote:
every time I try to
use the formatting features, nothing happens.
Wild guess: you're using a fairly recent version of IE on Windows.
On re-reading this, I see that my post looks like pure speculation, but
it's
Thus said Baruch Burstein on Thu, 07 Aug 2014 17:59:08 +0300:
The idea of just clicking on 2 revisions in the timeline to get a diff
is very convenient, but I would like to suggest a small improvement:
No matter what order I click the boxes in, it should display the diff
from the older to
On Thu, Aug 7, 2014 at 11:54 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
Personally, I like the current behavior. I determine the order in which
agreed, but..
Seems natural. Maybe a ``reverse order'' button when viewing the diff
would be useful though?
See the Invert button.
Thus said Warren Young on Thu, 07 Aug 2014 13:50:18 -0600:
This is beginning to sound like my outside contributions feature
request, a.k.a. uber-patch: http://goo.gl/4lLAuY
Yes, it is, and I had that same thought as I typed it, but, it can
already be accomplished with Fossil clone to
On Thu, Aug 7, 2014 at 3:50 PM, Warren Young war...@etr-usa.com wrote:
This is beginning to sound like my outside contributions feature
request, a.k.a. uber-patch: http://goo.gl/4lLAuY
My idea was to allow untrusted outsiders to be able to send a richer
patch file than patch(1) allows, but
Thus said Stephan Beal on Thu, 07 Aug 2014 23:59:23 +0200:
Seems natural. Maybe a ``reverse order'' button when viewing the
diff would be useful though?
See the Invert button.
Well... ok then, I will! It's nice when something already exists. :-)
Thanks,
Andy
--
TAI64 timestamp:
On 8 Aug 2014, at 12:52 am, Sean Woods s...@seanwoods.com wrote:
Or you could ask me, since I wrote autosetup :-)
I appreciate your assistance and responsiveness.
glob.tcl is bundled up in the jimsh0 executable, but you can find it because
the source code is there - autosetup/jimsh0.c
On 8 Aug 2014, at 10:58 am, Steve Bennett ste...@workware.net.au wrote:
On 8 Aug 2014, at 12:52 am, Sean Woods s...@seanwoods.com wrote:
Or you could ask me, since I wrote autosetup :-)
I appreciate your assistance and responsiveness.
glob.tcl is bundled up in the jimsh0 executable,
I have fixed Jim Tcl, updated autosetup, and pushed a new version to the
'autosetup' branch.
Please test. If it looks ok, perhaps someone can pull it into trunk.
Woo hoo! It works! Bonzer!!
swoods@web75:Fossil-93fb7c774f$ ./fossil version
This is fossil version 1.25 [93fb7c774f]
Thus said Steve Bennett on Fri, 08 Aug 2014 12:30:52 +1000:
I have fixed Jim Tcl, updated autosetup, and pushed a new version to
the 'autosetup' branch.
Did you intend for the branch to split off of such an old revision of
trunk?
Thanks,
Andy
--
TAI64 timestamp: 400053e44780
On 8 Aug 2014, at 1:43 pm, Andy Bradford
amb-sendok-1410061405.efmchampahhhjobco...@bradfords.org wrote:
Thus said Steve Bennett on Fri, 08 Aug 2014 12:30:52 +1000:
I have fixed Jim Tcl, updated autosetup, and pushed a new version to
the 'autosetup' branch.
Did you intend for the
Thus said Steve Bennett on Fri, 08 Aug 2014 14:00:02 +1000:
No. Not sure why that happened. I'm out of practice with fossil.
Well, it looks like Joe decided to merge trunk into the branch, so it
may not be anything to worry about. I started to look at it and there
were a lot of
Thus said Joe Mistachkin on Thu, 07 Aug 2014 21:14:56 -0700:
Yeah, it appears the net change was that Jim Tcl was updated. There
are quite a lot of changes to it since the last version. However, I
think it should be fine merging it to trunk? Any conflicting opinions?
No, looks fine now
On 8 Aug 2014, at 2:14 pm, Joe Mistachkin sql...@mistachkin.com wrote:
Andy Bradford wrote:
Well, it looks like Joe decided to merge trunk into the branch, so it
may not be anything to worry about.
Yeah, it appears the net change was that Jim Tcl was updated. There are
quite a
24 matches
Mail list logo
