On Nov 13, 2014 7:20 AM, "Stephan Beal" wrote:
>
> On Wed, Nov 12, 2014 at 10:16 PM, wrote:
>>
>> When opening a repo, if you select to overwrite all files, and a file to
be updated happens to be read-only (R attrib set), the overwrite fails (it
should) but if you then change the read-only to rea
On 11/6/14, jose isaias cabrera wrote:
>
> Greetings!
>
> First of all, I want to thank you whomever was the creator of this wonderful
>
> utility. Props to you.
That'd be drh (Richard Hipp) and a collection of contributors.
> I have a setup on my Windows PC where I have many sources of variou
I got same error msg on first web request, and then hit reload and it
worked fine.
-bch
On 10/30/14, Richard Hipp wrote:
> On Thu, Oct 30, 2014 at 2:53 PM, Warren Young wrote:
>
>> I just updated my Fossil server from version [e061a675e6] 2014-09-26
>> 21:02:03 to the tip of trunk, as of a few
On 10/28/14, Baruch Burstein wrote:
> On Tue, Oct 28, 2014 at 11:25 PM, Richard Hipp wrote:
>
>> Just be VERY CAREFUL that you don't add an artifact that is also used in
>> some other check-out that you want to keep, because after you shun it
>> will
>> be gone forever.
>>
>
> Shouldn't the shunn
On 10/28/14, Richard Hipp wrote:
> On Tue, Oct 28, 2014 at 5:17 PM, Ron W wrote:
>
>> Maybe could be as simple as adding the relevant artifact IDs to the shun
>> list and rebuilding. (Though that would be rather slow (which is not
>> necessarily a bad thing for this feature)).
>>
>>
> Yep. Just
Ron W wrote:
> On Tue, Oct 28, 2014 at 2:21 PM, Stephan Beal
> wrote:
>
>> On Tue, Oct 28, 2014 at 7:14 PM, B Harder wrote:
>>>
>>> 3) I can't think of anything else...
>>>
>>
>> You will.
>>
>
> Perhaps looking at how shunni
se of this
development whereby perhaps a single card/obj could be deleted, and
the "dangling" bits would be culled w/ a [f rebuild] ?
3) I can't think of anything else...
-bch
On 10/28/14, Stephan Beal wrote:
> On Tue, Oct 28, 2014 at 7:05 PM, B Harder wrote:
>
>> Are r
ference and delta removed/replaced properly is
> remarkably
> difficult.
Are references "backward", "forward", or both ? What I mean is,
roughly, is fossil a doubly linked list, or singly, and if single,
what direction?
-bch
On 10/28/14, Richard Hipp wrote:
> On Tue, O
On 10/28/14, Jungle Boogie wrote:
> Dear Richard,
>
> From: Richard Hipp
> Sent: Tue, 28 Oct 2014 10:09:25 -0400
> To: Fossil SCM user's discussion
> Subject: Re: [fossil-users] Fossil checksum
> >
>> On Tue, Oct 28, 2014 at 10:00 AM, Stephan Beal
/23/14, Richard Hipp wrote:
> On Thu, Oct 23, 2014 at 10:20 AM, B Harder wrote:
>
>> kamloops$ fossil open ../fossils/netbsd_src.fsl
>> SQLITE_CORRUPT: database corruption at line 53640 of [e4ab094f8a]
>> SQLITE_CORRUPT: database corruption at line 53679 of [e4ab094f8a]
>
kamloops$ fossil open ../fossils/netbsd_src.fsl
SQLITE_CORRUPT: database corruption at line 53640 of [e4ab094f8a]
SQLITE_CORRUPT: database corruption at line 53679 of [e4ab094f8a]
SQLITE_CORRUPT: statement aborts at 3: [SELECT 1 FROM event WHERE type='ci']
fossil: SQL error: database disk image is
I'm maintaining a large(ish) repo for production deployments of
various software like Apache httpd, OpenSSL, etc.
What I have is a [vendor] branch for the vanilla vendor software (ie:
httpd-2.2.27.tar.gz), and "feature branches" for configuration/tweaks
(ie: [redhat_build] for building for redhat
Arguably, if you need empty dirs in your project as part of a build
process, it should be in the Makefile or equiv.
-bch
On 10/6/14, Gaurav M. Bhandarkar wrote:
> maybe you could use :
> fossil settings empty-dirs
>
> A comma or newline-separated list of pathnames. On
> update and checkout comma
On Oct 2, 2014 11:14 AM, "Andy Bradford" wrote:
>
> Thus said Stephan Beal on Thu, 02 Oct 2014 19:31:12 +0200:
>
> > The weird thing is, he's got two "initial empty commits". i'm at a
> > loss to explain that.
>
> Seems that one of them must have been created with an older fossil and
> the
Hi Dave.
This is a "fork" (unintentional branch). It would happen (for example)
if two different clones of a repository are updated independently of
each other, and then sync'd. You can merge the "errant trunk" back to
the "good trunk" without ill effect (minding you might have to do
conflict reso
I haven't had time to dig in, but that sounds like the ticket I opened this
week. If it sounds like that to you too, kindly add any more relevant info
you have:
http://fossil-scm.org/index.html/tktview?name=94a1f83f9f
On Sep 12, 2014 9:12 PM, "Philip Bennefall" wrote:
> Hi all,
>
> I am running
On Sep 6, 2014 11:11 AM, "Stephan Beal" wrote:
>
> On Fri, Sep 5, 2014 at 10:07 PM, Philip Bennefall
wrote:
>>
>> whether it should really say branch rather than tags. Is this a bug, or
is it really meant to be branch rather than tags?
>
>
> It's probably just an oversight. IIRC, the --tag option
https://news.ycombinator.com/item?id=8265249
Github gets "split diffs", everybody rejoices.
-bch
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On 8/6/14, Ron W wrote:
> On Tue, Aug 5, 2014 at 5:16 PM, Warren Young wrote:
>
>> On 7/26/2014 08:53, Eric Rubin-Smith wrote:
>>
>>>
>>> * Code review!
>>>
>>
>> Your talk of state machines suggests that you're instead envisioning a
>> system where you can't get a checkin into the trunk -- may
I'm on mobile device - please excuse typos/brevity.
I managed a team of about 10 local committers (in my office) and about 10
more remote (across the country).
I had a FreeBSD production environment. I setup a FreeBSD dev/testing
environment where everybody was isolated by jails, and had their ow
Quotable:
I must say that Fossil is the best thing to happen
to my development workflow this year, as I am pretty sure that using
Git has resulted in the premature death of too many of my brain cells.
I'm glad to be able to replace Git in every place that I possibly can
with Fossil.
On Jul 25, 201
My bindings for curses are pretty low-level, and I build functions to sort
of act as macros where I want convenience, fwiw. I think it's important to
honor the existing culture (ie: addressing in lines, columns versus more
typical x,y) even though it's not how one might build it today.
$0.02
-bch
On 7/17/14, Andy Goth wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 7/17/2014 3:22 PM, Stephan Beal wrote:
>> in terms of memory use, it seems to be on par with lua, and lua is
>> the lightest-memory interpreter i've yet run through valgrind. Most
>> of them individually leak mor
On Jul 10, 2014 9:24 PM, "Timothy Beyer" wrote:
>
> At Thu, 10 Jul 2014 20:10:09 -0700,
> B Harder wrote:
> >
> > It's clear people are split on what The Right Thing To Do is re:
symliks.
> >
> > I'm personally not sure; I don't use
It's clear people are split on what The Right Thing To Do is re: symliks.
I'm personally not sure; I don't use them in the course of development.
That said, I feel like they should *not* be in indirrected-through as a
matter of treatment. It's understandable those that _would_ like them to be
foll
Good catch: you're correct.
-bch
On 7/7/14, Stephan Beal wrote:
> On Mon, Jul 7, 2014 at 10:10 PM, B Harder wrote:
>
>> Fossil insures that no remote user will ever be able to remove
>>
>
> Shouldn't that be "ensures"? i always confuse
esting and receiving all SHUN >records. You can
>
>>disable this using
>>
>> "fossil setting auto-shun off"
>
>
>
>
> On Sun, Jul 6, 2014 at 3:10 PM, Andy Bradford
> wrote:
>
>> Thus said B Harder on Sun, 06 Jul 2014 14:40:58 -0700:
&g
myhost$ fossil pull
Pull from http://joeb...@fossil-scm.org
Round-trips: 1 Artifacts sent: 0 received: 74
Pull finished with 439 bytes sent, 2645 bytes received
myhost$ fossil pull http://joeb...@fossil-scm.org --http-trace
Round-trips: 1 Artifacts sent: 0 received: 0
Pull finished with 425 b
What are the "artifacts received" below? Is these administrative, or
is there something else at play?
myhost$ fossil pull
Pull from http://joeb...@fossil-scm.org
Round-trips: 1 Artifacts sent: 0 received: 74
Pull finished with 442 bytes sent, 2308 bytes received
myhost$ fossil pull
Pull from ht
On Jun 30, 2014 2:20 AM, "Jan Nijtmans" wrote:
>
> 2014-06-27 23:40 GMT+02:00 Andy Goth :
> > How come events are always shown with (at least) sixteen digits on the
> > timeline whereas other artifacts are given ten digits?
> >
> > http://www.fossil-scm.org/fossil/timeline?n=20&y=e
>
> Just becaus
If everything is (ultimately) spawned from the "initial empty
checkin", how can I be getting "WARNING - no common ancestor: "
when merging one branch into another ?
-bch
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-
On Jun 17, 2014 10:47 AM, "Stephan Beal" wrote:
>
> On Tue, Jun 17, 2014 at 7:24 PM, B Harder wrote:
>>
>> Nice! As a BSD user though, I feel compelled to point out this looks
>> like a readline[1] feature, and not an editline[2] feature. So it
>> wo
On 6/17/14, Stephan Beal wrote:
> On Tue, Jun 17, 2014 at 6:49 AM, B Harder wrote:
>
>> Remember that the buffer is only one level deep, though. A subsequent ^W,
>> ^K , etc will clobber the previous contents.
>>
>
> Almost: try 2x (NON-consecutively) ctrl-k (or
Remember that the buffer is only one level deep, though. A subsequent ^W,
^K , etc will clobber the previous contents.
Along lines of Stephan Beals method, I use ":" preceding the fossil
command. So:
$ : fossil ci -m 'some msg'
("$" is shell prompt).
":" is a command that consumes it's argument
Cscope (+1) knows much more than just C.
On Jun 15, 2014 2:17 PM, "Sergei Gavrikov"
wrote:
> On Sun, 15 Jun 2014, Sean Woods wrote:
>
> > Dear List,
> >
> > I am hacking on a large, complicated code base in my spare time for
> > fun. I unzipped the tarball with many source files and imported it
Fossil certainly will spawn external programs if you:
1) start a commit w/o a command-line commit message
2) run a did with an external diff-command configured.
, maybe others.
On Jun 7, 2014 12:00 PM, "Ron Wilson" wrote:
> On Sat, Jun 7, 2014 at 11:52 AM, Stephan Beal
> wrote:
>
>>
>> On Sat
Hey Nico --
Some thought-provoking comments. Thanks.
-bch
On 6/7/14, Gour wrote:
> Nico Williams writes:
>
>> I wouldn't, don't, and won't demand that anyone follow such a workflow
>> for
>> any codebase I don't own, and possibly not for codebases I own either
>> (depends). I only want to be
On Jun 5, 2014 10:55 AM, "Richard Hipp" wrote:
>
>
>
>
> On Thu, Jun 5, 2014 at 1:37 PM, Andy Bradford
wrote:
>>
>> Thus said Warren Young on Thu, 05 Jun 2014 09:25:39 -0600:
>>
>> > A contribution from an untrusted outsider needs to be checked
>> > carefully before it is committed to th
drh> Fossil allows you to commit a subset of files (by listing the
files on the "fossil commit" command line) but there is no mechanism
for committing a subset of lines within a single file.
That, and there _are_ branches/tags which are encouraged to be used...
my prev comment was for the case whe
I've heard git allows this, and occasionally wished for it.
As it stands currently, it's not possible with fossil. There is a degree of
freedom in this regard using the fossil "stash", though, which can be used
with some file jigging to separate two (or more?) logical ideas that one
wants committe
sb> fossil bk add xp experimental:2011-06-04
I can imagine this being useful at least occasionally. I'm still
loathe to include it in core fossil, but it'd be a great task for a
little tool.
-bch
On 6/4/14, B Harder wrote:
> Because the internet can be a poor medium to e
ID, and runs 'exec ("fossil co $UUID");'.
-bch
On 6/4/14, Stephan Beal wrote:
> On Wed, Jun 4, 2014 at 6:53 PM, B Harder wrote:
>
>> Indeed, non-propagating tags are also "checkout-able" items.
>>
>> What am I missing about bookmarks that
Indeed, non-propagating tags are also "checkout-able" items.
What am I missing about bookmarks that we can't already enjoy w/ tags,
outside of new syntax ?
-bch
On 6/4/14, Richard Hipp wrote:
> On Wed, Jun 4, 2014 at 12:03 PM, Nico Williams
> wrote:
>
>> On Wed, Jun 4, 2014 at 9:07 AM, Stepha
> Maybe convince the git developers to move their metadata into sqlite instead?
Ha! Thanks for putting a smile on my face Stephan.
-bch
On 6/3/14, Stephan Beal wrote:
> On Tue, Jun 3, 2014 at 7:09 PM, Stephan Beal wrote:
>
>> precision differences in 4 records (0.24%) when converting those
>>
I think drh unnecessarily missed an opportunity there. He seemed to work
harder to obfuscate what fossil actually was than giving a single passing
description and moving on with his talk about SQL and using fossil by name
where it's used as an example.
Otherwise, interesting talk!
On Jun 1, 2014 8
http://mikegerwitz.com/papers/git-horror-story
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Stephan - i'm on mobile ATM so will be brief, but you and I did discussed
this offline weeks ago whereby I thought we agreed that changing the text
of the initial commit to something symbolic ("."?) or inoffensive Latin
("seed ", "origin") really would fit the bill without rejigging core fossil
ope
IIUC:
you: fossil clone http://sqlite.org:8080 fossils/sqlite.fsl; cd
project_dir; fossil open ~/project_dir/sqlite.fsl; fossil server
Each of your our co-conspirators: fossil clone
http://your.machine.address:8080 fossils/sqlite.fsl; cd project_dir; fossil
open ~/fossils/sqlite.fsl
You will: fo
I was going to +1 sbeals idea, but the pull-only autosync note came up, and
now I think I may not know all there is about autosync. Thanks for keeping
it interesting, folks.
On May 29, 2014 8:34 PM, "Andy Bradford" wrote:
> Thus said Stephan Beal on Thu, 29 May 2014 22:10:24 +0200:
>
> > Wasn't e
Stephan Beal wrote:
> On Wed, May 14, 2014 at 11:22 PM, B Harder wrote:
>
>> Andy, to be clear, are you suggesting:
>>
>> a) blah blah [cafebabe] blah blah blah
>>
>
> My comments assumed this interpretation. To my eyes that looks a tiny bit
> cleaner, bu
Andy, to be clear, are you suggesting:
a) blah blah [cafebabe] blah blah blah
b) blah blah cafebabe blah blah blah
?
-bch
On 5/14/14, Joseph Prostko wrote:
> On Wed, May 14, 2014 at 2:38 PM, Andy Goth wrote:
>> I'd like for the [bracket] characters to not be part of the ...
>> links
>>
The $EDITOR idea is the first thing I thought of when reading the
Stephens initial post. Low barrier to entry, high effort/reward ratio.
A curses interface would be sexy (for some definition), but I'd say a
distant second as far as functional desirability.
-bch
On 5/7/14, Stephan Beal wrote:
>
I restrained myself in the previous discussion that ended up being about
the initial empty commit, but now I feel compelled: the rational,
"discussion", and decision to remove the initial empty commit were pretty
poor, IMO. I don't want to belabor the point, so I'll leave it at that.
Happy to disc
I think that initial empty commits went in at my request. Iirc, so I could
have related (but not inheriting from trunk) vendor branches. Can we
review/discuss before axing?
On May 1, 2014 1:06 AM, "Jan Nijtmans" wrote:
> 2014-05-01 7:24 GMT+02:00 Gerald Gutierrez :
> > So now I'm confused. Should
On 4/14/14, David Given wrote:
> On 4/14/14, 9:31 PM, B Harder wrote:
> [...]
>> Our users shouldn't need CVS, SVN, etc experience to know this. I
>> added documentation to clarify.
>
> It might also be useful to add:
>
> # (To abort the commit, leave this f
On 4/14/14, Martin Gagnon wrote:
> Le 14 avr. 2014 11:48, "Stephan Beal" a écrit :
>>
>> On Mon, Apr 14, 2014 at 3:39 PM, Tony Papadimitriou
>> wrote:
>>>
>>> But, in my defense, (and I just re-read it to be sure I didn't miss it)
> nowhere in the help documentation (FOSSIL HELP COMMIT) or the c
That sounds like a bad idea to me. IMO, this is a case of "good enough"
getting in the way of "good" as far as solutions to your annoyance.
Off the top of my head, I can think of two workflow habits that may help
you:
1) set up/turn on gpg signing, so you'll be required to sign commits before
the
I think th1 "happens" to basically be a subset of Tcl, but is not
"designed" to strictly be a subset of Tcl, fwiw.
On 4/4/14, Jan Nijtmans wrote:
> 2014-04-04 10:54 GMT+02:00 Mark Janssen :
>> Why can't n-ary numbers have dots? 0b1.11 is a perfectly valid
>> representation of 1.75.
>
> $ tcls
On 1/14/14, Andy Bradford wrote:
> Hello,
>
> While attempting to pull the Fossil repository, I saw this error:
>
> $ fossil up
> Autosync: https://www.fossil-scm.org/
> Round-trips: 2 Artifacts sent: 0 received: 0
> Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT
>
_WHY_ does --disable-internal-sqlite (and the unknown versions of
SQLite that follow) have to be supported ?
If package/OS maintainers insist on hacking in alien shared-lib
SQLite, let them own their hacks and the repercussions.
Call it a major version# bump, and remove that support.
-bch
On 1/
If I understand what you're looking for (first empty commit?), when I asked
this question some time ago, somebody suggested I just tag it myself.
Simple solution, Just Works.
On Dec 20, 2013 8:54 PM, "Andy Bradford" wrote:
> Thus said Richard Hipp on Fri, 20 Dec 2013 19:05:07 -0500:
>
> > htt
WARNING - no common ancestor:
WARNING - no common ancestor:
WARNING - no common ancestor:
...
On 10/10/13, B Harder wrote:
> closed/opened my more complex real-world problem repo and problem still
> exists.
>
> On 10/10/13, B Harder wrote:
>> hrmmm... interesting.
>&
closed/opened my more complex real-world problem repo and problem still exists.
On 10/10/13, B Harder wrote:
> hrmmm... interesting.
>
> I was getting "no common ancestor".
>
> I closed that repo to mail it. You did you testing (successfully). I
> re-opened the repo
going to close/open my test/clone "problem" repo.
On 10/10/13, Stephan Beal wrote:
> On Thu, Oct 10, 2013 at 7:31 PM, B Harder wrote:
>
>> Breakthrough!
>>
>> I have a minimal(ish) example of a repo that is broken:
>>
>> Take the attached (broke
> the ui to "make a branch" trunk in several nodes along the trunk timeline
> until one of them worked. Try it disconnected do as not to mess up the
> original db.
> On Oct 9, 2013 3:26 PM, "B Harder" wrote:
>
>> I know what you're talking about, but I&
ng raw tags. Start with fossil tag list
> --raw checkin. Then I think you should be able to cancel the offending raw
> tag.
> On 9 Oct 2013 23:07, "B Harder" wrote:
>
>> ...and now I see the edit where the trunk tag was cancelled --
>> question remains --- can I un
...and now I see the edit where the trunk tag was cancelled --
question remains --- can I undo/reverse the effect?
On 10/9/13, B Harder wrote:
> It appears that somehow the branch tag was deleted on my [trunk].
>
> Now, when I try to merge from trunk -> feature_branch, I get some
It appears that somehow the branch tag was deleted on my [trunk].
Now, when I try to merge from trunk -> feature_branch, I get something like:
$ fossil merge trunk
WARNING - no common ancestor: filea.c
WARNING - no common ancestor: fileb.c
WARNING - no common ancestor: filec.c
...
ADDED src/othe
On Sep 19, 2013 1:38 AM, "Stephan Beal" wrote:
>
> Hi, all,
>
> some people have bemoaned Fossil's lack of file permissions support over
the years. Initially, Fossil did not track _any_ permissions, but the
executable bit was eventually added because it is common practice to have
an executable con
I read this roughly (in fossil-speak) as:
"I had a bunch of email notes from folks requesting I merge their
feature-branches into my main branch, but my machine crashed and my mail
isn't accessible…"
I think auto-sync wouldn't have saved anything, but perhaps the something
like fossils built-in t
fossil set tracker [on|off] ?
On Sep 11, 2013 2:32 PM, "Stephan Beal" wrote:
> On Wed, Sep 11, 2013 at 11:26 PM, Kees Nuyt wrote:
>
>> I wouldn't mind logging the arguments as well, especially for commands
>> that modify the repository or a stash.
>>
>
> i considered it, but the code overhead ju
'm personally
fine w/ that, if it's an option.
Cheers,
-bch
On 8/29/13, Richard Hipp wrote:
> On Fri, Aug 30, 2013 at 12:35 AM, B Harder wrote:
>
>> I don't know what the definition of "recent" is, but I think my password
>> is same for months, wasn&
I don't know what the definition of "recent" is, but I think my password is
same for months, wasn't working at time I sent last msg. I'll work with you
off-list if necessary.
Thanks drh,
-bch
On Aug 29, 2013 8:12 PM, "Richard Hipp" wrote:
>
>
>
Did this nuke accounts/passwords ?
On 8/29/13, Richard Hipp wrote:
> On Thu, Aug 29, 2013 at 5:33 PM, Joerg Sonnenberger
> > wrote:
>
>> On Thu, Aug 29, 2013 at 04:50:19PM -0400, Richard Hipp wrote:
>> > The database corruption was caused by scenario 1.1 at
>> > http://www.sqlite.org/howtocorrupt
On Aug 22, 2013 7:58 AM, "Stephan Beal" wrote:
>
> On Thu, Aug 22, 2013 at 10:45 AM, Stephan Beal
wrote:
>>
>> On Thu, Aug 22, 2013 at 4:34 AM, Chad Perrin wrote:
>>>
>>> I'd say the name should just be set in stone as libfossil now, and a
>>
>>
>> i tend to agree. But then we'll have to find an
Agreed. Hyphens in libnames don't look pleasing to my eye (fwiw),
libfossilscm (cc ... -lfossilscm ...) might be next best to
disambiguate from potential collision w/ another libfossil, though it
too is pretty ugly looking.
Brief search yields https://github.com/paulfitz/libfossil as second
hit (a
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.
Very glad you like it.
On Aug 10, 2013 10:55 PM, "Sam Sellars" wrote:
> Thank you sir! This is exactly the type of thing I am looking for. I
> appreciate the time you put into this.
>
>
> —
>
>> Hi Sam.
>>
>> Welcome aboard. I think Fossil is excellent, and I hope you will too.
>>
>> I'm typing
Hi Sam.
Welcome aboard. I think Fossil is excellent, and I hope you will too.
I'm typing on a mobile device ATM, so please excuse the brevity and
spelling errors.
I use fossil for all my personal projects, as well as professionally. For
personal projects, I make a project-specific dir under my p
On Aug 3, 2013 7:09 AM, "Stephan Beal" wrote:
>
> On Sat, Aug 3, 2013 at 3:36 PM, Gour wrote:
>>
>> a) Search feature seems to be addressed, right?
>
>
> Yes.
>
>>
>> b) uncomit - ability to simply uncommit last commit which I'd do while
>> still staying in my local repo and prior to pushing any
a la libiberty?
cc -o foo foo.c -liberty
On 7/31/13, Stephan Beal wrote:
> On Wed, Jul 31, 2013 at 10:32 PM, B Harder wrote:
>
>> I'm going to recycle a project name I've used before: urvogel (the first
>> bird), and suggest for its logo:
>> http://www.ucmp.b
I'm going to recycle a project name I've used before: urvogel (the first
bird), and suggest for its logo:
http://www.ucmp.berkeley.edu/diapsids/birds/archie2.jpg
On Jul 30, 2013 3:06 AM, "Stephan Beal" wrote:
> Hi, all,
>
> As most of you know, work has begun on a prototype of what i unfortunatel
I'd suggest: fossil is happy to run wherever it can, and strives for
portability wherever it can, whenever it makes sense.
Any OS is welcome to modify/redistribute fossil in the terms described in
the license.
It sounds to me (correct me if I'm wrong) you are asking "what (or how
many?) operating
I think these things support each other. Specifically, with respect to Tcl
(and likely Guile, Lua), scripting support can come by embedding the Tcl
interpreter inside the app (ie: the standalone fossil executable), by
linking libtcl with fossil, and having fossil call into it appropriately.
Altern
I personally have no objections, but as a matter of business and
visibility, perhaps do final "last call for objections/alternatives!" on a
business day.
On Jul 23, 2013 12:59 PM, "Stephan Beal" wrote:
> On Sun, Jul 21, 2013 at 7:49 PM, Richard Hipp wrote:
>
>>
>>
>> On Sun, Jul 21, 2013 at 11:4
On 7/17/13, Edward Berner wrote:
> Hello,
>
> Using a recent trunk version of fossil, built with gcc on Solaris 10 on
> an UltraSPARC system, I get a bus error from "fossil new":
>
> $ ./fossil new t.fossil
> Bus Error (core dumped)
>
>
> $ ./fossil version -v
> This is fossil version 1.26 [5d74ce
On Jul 17, 2013 12:58 AM, "Stephan Beal" wrote:
>
>
> On Wed, Jul 17, 2013 at 12:35 AM, B Harder wrote:
>>
>> Of top of head, reflexive position is that week numbers are running in
wrong order, but if it's reversed, latest would be at bottom of page.
>
>
Of top of head, reflexive position is that week numbers are running in
wrong order, but if it's reversed, latest would be at bottom of page. That
made me wonder though, what of vertical bars vs. horizontal?
Just tossing ideas...
On Jul 16, 2013 1:50 PM, "Stephan Beal" wrote:
> On Tue, Jul 16, 20
Very cool, Stephan!
On Jul 16, 2013 1:30 PM, "Stephan Beal" wrote:
> On Tue, Jul 16, 2013 at 6:49 PM, Matt Welland wrote:
>
>> This looks cool. Will this data be available via the json interface?
>> Being able to aggregate the stats over a lot of different fossils would be
>> useful to some of u
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
>>
** 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
>>>
>>> Com
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]
>
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 Jun 21, 2013 11:02 AM, "Richard Hipp" wrote:
>
>
>
> On Fri, Jun 21, 2013 at 1:35 PM, B Harder wrote:
>>
>> I realize this check is early in the commit phase, but now I wonder:
barring pushed/autosync'd content, can one "pop" or unwind the la
On Jun 21, 2013 9:32 AM, "Stephan Beal" wrote:
>
> Hiho,
>
> In a repo of mine (not fossil) i just made a commit faux pas by not
entering the _one_ filename i wanted on the command line, and instead
committing several others i wasn't ready to commit. So now i want to add a
fossil feature but thoug
I reran ./configure, make clean, make and things look good on my end
now too. Apologies for the noise.
-bch
On 4/29/13, Richard Hipp wrote:
> On Mon, Apr 29, 2013 at 7:25 PM, Richard Hipp wrote:
>
>>
>>
>> On Mon, Apr 29, 2013 at 6:55 PM, B Harder wrote:
>>
Thx for the test drh. I'll see what I can on my end.
On 4/29/13, Richard Hipp wrote:
> On Mon, Apr 29, 2013 at 6:55 PM, B Harder wrote:
>
>> Fossil trunk [748f975345] generates a binary that immediate segfaults.
>> My env is:
>>
>> NetBSD kamloops 6.99.19 Net
Fossil trunk [748f975345] generates a binary that immediate segfaults.
My env is:
NetBSD kamloops 6.99.19 NetBSD 6.99.19 (GENERIC) #149: Mon Apr 29
11:57:00 PDT 2013
root@kamloops:/usr/obj/sys/arch/amd64/compile/GENERIC amd64
I haven't had a change to triage this yet, and fossil's ticket system
i
98 matches
Mail list logo
