Please, when merging branches that will end up in the repo, merge INTO
master before pushing, as opposed to merging master to feature branch.
Example:
commit 4158a412c3ed75c027a47996b52057e812e8b5ed
Merge: 50e98da... 9b5eaf9...
Author: Francois-Rene Rideau f...@tunes.org
Date: Fri Mar 12
On 13 March 2010 13:19, Nikodemus Siivola nikode...@random-state.net wrote:
commit 4158a412c3ed75c027a47996b52057e812e8b5ed
Merge: 50e98da... 9b5eaf9...
Author: Francois-Rene Rideau f...@tunes.org
Date: Fri Mar 12 10:51:42 2010 -0500
Merge branch 'master' of
On 12 March 2010 07:24, Faré fah...@gmail.com wrote:
Well, apart from ~/.local/share/ being a standard XDG-recommended
place to store such things, consider that
Erm, my reading suggests otherwise.
From:
http://standards.freedesktop.org/basedir-spec/latest/ar01s03.html
$XDG_DATA_HOME
On Sat, Mar 13, 2010 at 12:01 PM, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
I must admit that after four hours fighting with this I am right now a bit
pissed off, so please forgive the tone of the message.
ASDF has introduced a new caching system which alters the
On Sat, Mar 13, 2010 at 4:40 PM, Faré fah...@gmail.com wrote:
It's also what I committed to 1.634.
Thanks for your explanations and corrections. I just updated ECL to use
1.634.
FYI, the reason why I did not add **/*.* is because the sbcl case was just
specified like that: (getenv SBCL_HOME),
: Juanjo
I was just thinking how to extend this functionality to user-defined systems
and hit another problem. The goal is to take an ASDF system and prepare a
bundle that contains a PREBUILT-SYSTEM file (*.asd), a library file (*.a or
*.lib) and a FASL (*.fas) This set of files can then be
On Sat, Mar 13, 2010 at 8:50 PM, Faré fah...@gmail.com wrote:
Where is the file to be when you compile?
Where is the file to be when you load?
How do you currently do things, and what breaks?
Could say, a logical pathname host LIB:
help locate the libraries?
How do you do things without
On 3/13/10 Mar 13 -1:12 PM, Faré wrote:
We could adopt the same algorithm as dpkg or rpm uses for comparing version.
I once implemented it in shell script. Could do it in Lisp...
I confess to not really knowing this algorithm (I haven't built an RPM
in a long time), nor having any guess about
I had to do this quite quickly, so the import was a bit rough and ready.
BTW, I think the two configuration chapters should be pushed UP in the
manual, and the object model should be pushed DOWN below them, since the
former is for advanced users, but the latter is for in-depth programmers.
The
On 13 March 2010 16:56, Robert Goldman rpgold...@sift.info wrote:
On 3/13/10 Mar 13 -1:12 PM, Faré wrote:
We could adopt the same algorithm as dpkg or rpm uses for comparing version.
I once implemented it in shell script. Could do it in Lisp...
I confess to not really knowing this algorithm
10 matches
Mail list logo
