-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Levitte - VMS Whacker wrote:
Now, I'm trying to figure out what's happening, exactly, so I can fix
the problem. To begin with, I think I need a pointer to where '_' is
defined. It's incredibly difficult to find among all other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathaniel Smith wrote:
Can any of the win32-clued people out there shed any more light on this?
Windows' CMD.EXE shell always had binary-safeness in its pipes.
I'm not quite sure of the current support of it, tough, as I'm a quite
happy CygWin user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Jones wrote:
I appreciate that many people copy and paste - all that means is that
we should use underscores to seperate the digit groups.
Or, rather, that any different method of printing them should be
optional and not a default choice (i.e.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there.
Each time I decide to version a binary or executable file I wonder: is
there a specific reason to put the attributes in a .mt-attrs file in the
same directory of the referenced file instead of, as an example, storing
it in the MT/ directory,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
Another good idea I read in this thread was the --output option, that
would be useless in any case (to write a file directly, avoiding pipes)
and would work for sure even in plain Windows.
UseFUL, not useLESS, silly me.
(IMHO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timothy Brownawell wrote:
It's in the project root dir, regardless of which subdirs the referenced
files may be in.
Oh, my fault.
It's that things in MT/ are not allowed to be versioned. So, any control
files that do need versioning are named
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there.
This evening I extracted monotone sources in order to start an italian
translation in po/it.po and I noticed that it did fail to recognize
libboost_test unless some patches were applied.
Has any one of the mani developers took a look at them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christof Petig wrote:
Can we please agree to tackle win32 after inclusion in mainline? I don't
want to spend hours on that again.
BTW: as I have decided that monotone is the VCS for me I intend to
contribute to it, specifically in the OS I use:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Weimer wrote:
Can you say how it handles a CVS history where some files have been
re-tagged?
Is re-tagging visible in the CVS repository at all?
AFAIK/AFAIR tags are *not* versioned, in CVS.
- --
L a p o L u c h i n i
l a p o @ l a p o .
to
be the lack of Boost::test in cygwin's port of Boost.
(I *will* look into that, after my thesis is finished ^_^)
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (ICQ UIN: 529796)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
Comment: Using GnuPG with Thunderbird
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isn't sqlite supposed to be binary-safe?
Well, except from \0, AFAIR, but shouldn't avoiding that be way faster
and smaller than full base64?
OK, HDD is cheap, but wasting 1/3 of the space and using a system that
is designed to be binary safe seems a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
Can any of the win32-clued people out there shed any more light on this?
Windows' CMD.EXE shell always had binary-safeness in its pipes.
I guess I was drunk or crazy or had hit the head the day I wrote that
message. What I meant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Weimer wrote:
I think you can do this with BLOBs.
Of course, but INTEGERs are automatically converted in a .dump ;-)
| BLOB literals are string literals containing hexadecimal data
Oh, I *really* didn't notice they were represented as an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
I will definitely ask them about it. =)
For tracking, it is ticket #1451:
http://www.sqlite.org/cvstrac/tktview?tn=1451
- --
L a p o L u c h i n i
l a p o @ l a p o . i t
w w w . l a p o . i t /
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Karpinski wrote:
Monotone reports the following bug. Here's the short version:
monotone: fatal: std::exception: Botan: ARC4 cannot accept a key of
length 33
Passwords should really ALWAYS be passed through an hash before being
used as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
For tracking, it is ticket #1451:
http://www.sqlite.org/cvstrac/tktview?tn=1451
2005-Sep-26 01:49:33 by drh:
The built-in quote() function converts BLOBs into ascii BLOB literals.
Whooops... I didn't notice it ^_^
So I guess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry Hastings wrote:
Let me be clear: I am hardly opposed to changing these tags to custom
certs. Indeed, that could offer its own advantages. But I am curious
about the reaction of the general *monotone* community. I am now well
acquainted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I mentioned as a side note in a couple of threads, but maybe it's time
to state it plainly: I began translating monotone to italian ;-)
I translated just 98 strings, but it's a start...
My latest version is c3c8753c9bb71a26f932343bdd6f1d1bd83b278a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christof Petig wrote:
$ mt pull -k cyberx.lapo.it net.venge.monotone\* monotone:
warning: protocol error while processing peer cyberx.lapo.it:
'received network error: anonymous access to branch
'net.venge.monotone' denied by server' monotone:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wim Oudshoorn wrote:
If instead of the current mechanism it would
be possible to have something like
This is scary: believe or not I was just about to propose something
close to that myself =)
(that is: FWIW I completely agree about the proposal)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Levitte - VMS Whacker wrote:
I think you're operating under some false assumptions. Just because a
certificate was revoked yesterday, it doesn't mean that a signature
made a week ago suddenly becomes invalid.
EXCEPT when the revocation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chad Walstrom wrote:
Could you give examples, or a test case to peruse?
Mhh, I was strictly thinking from a cryptography point of view, not
specifically in the monotone scenario, but let me think...
I ask this because it seems exceptionally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since a few weeks cygwin has got a precompiled boost package, so it
should be possible to compile monotone under cygwin.
Problem is (seems to be) that cygwin's boost doesn't include test
module (dunno what the problem is, I'm not the boost maintaner
Bruce Stephens wrote:
monotone stores binary deltas of the xdelta form, I believe
BTW bsdiff deltas should be quite more efficient than xdelta ones, but
they have an higher memory requierment and a somewhat funny license.
http://www.daemonology.net/bsdiff/
[...]
bsdiff routinely produces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Gregan wrote:
Since a few weeks cygwin has got a precompiled boost package, so it
should be possible to compile monotone under cygwin.
You could before, you just had to build Boost first.
Ehm, Yes. What I meant was: it should be now possible
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, it seems the old mantainer couldn't do it no more and as I care
for that particular port, I just took mantainership of it.
So, it seems that I'm the one to blame when the port doesn't... ehm, to
thank when the port works perfectly =P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Regarding viewmtn's current problem (hangs a lot a leaves lots of
www-owned monotone processes around) I was asking myself: chould be a
good idea anyway if automate had a timeout switch to tel him
something like wait for a command at most for 30
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there.
(this would be silly question #3)
OK, disk space is cheap, but I was wondering... why building
(exclusively) with a bundled popt, a bundled LUA, a bundled sqlite and a
bundled botan?
All of three have got critical flaws whose patches were
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems that monotone's configure lacks a test for wcswidth: 0.24
compiles no more under FreeBSD 4.x, which doesn't supply it.
I'll have some days away from home, I'll take a look at that (possibly
writing a FreeBSD4-specific patch) next week.
Just to let you know that monotone-0.25 likes Cygwin's latest libboost
enough to produce a working executably, and I am willing to produce an
official package for it, that people can install using
http://cygwin.com/setup.exe
make test, unfortunately, doesn't work as the boost unit test
While trying on FreeBSD the latest relase...
% monotone db migrate
[...]
% monotone db rosterify
monotone: converting existing revision graph to new roster-style revisions
monotone: certs in | certs out | nodes | revs out
monotone: 2255 | 0 | 560 |0
monotone: scanning for
Nathaniel Smith njs at pobox.com writes:
I.e., two different root revisions were created at different times
by running monotone setup twice, and then at some later point those
trees were merged.
I guess that's what happened while creating the homeidr branch on a couple of
hosts and then
Lapo Luchini lapo at lapo.it writes:
Just to let you know that monotone-0.25 likes Cygwin's latest libboost
enough to produce a working executably, and I am willing to produce an
official package for it, that people can install using
http://cygwin.com/setup.exe
Well, I did.
http
monotone: fatal: std::exception: boost::filesystem::is_directory:
/path/to/file: Too many levels of symbolic links
monotone:
monotone: this is almost certainly a bug in monotone.
It was, in fact, a symlink loop, not a bug i monotone =)
Lapo
___
Nathaniel Smith njs at pobox.com writes:
I wrote up a preliminary plan on what to do next on the delta storage
stuff, i.e., make some comparisons:
http://venge.net/monotone/wiki/DeltaStorageStrategies/ShootOut
I *may* also be the right time to evaluate different binary-diff schemes?
bsdiff
Nathaniel Smith njs at pobox.com writes:
Maybe. We can always do that later too, though -- holding up a fix
for initial pull speed in order to get minor improvements in database
size is probably not a good idea.
That's a very good point.
I guess it's important to test these things on real
Nathaniel Smith wrote:
Why switch?
-- Real-world usage shows, many many users do not like the long
name, and alias it to something shorter.
Yay for MTN!!!
I'm a mtn user since day 0, AFAIR I created the symlink even before
trying it ;-)
(and before discovering other people were using
[EMAIL PROTECTED] wrote:
Should we want to differentiate ourselves in google searches, perhaps
trying a few names on google now might be useful.
mmm -- 8,490,000 Google hits
mm -- 109,000,000
m -- 1,340,000,000
mtn -- 6,410,000
mon -- 206,000,000
monotone -- 2,950,000
But as Google
Nathaniel Smith njs at pobox.com writes:
To spoil the ending, I'm going to suggest we switch to the name mtn
for 0.26 and going forward.
I'm definitely for it... partly because I like innovation/change, but even more
so because it would be no change at all for me: as far as I remember I did
Shawn Samuel wrote:
I am willing to pay a good bounty for a reproducible build process for
monotone-viz on cygwin. That is, whatever needs to be done to
monotone-viz or to the environment that will get it to compile against
a basic cygwin installation, the monotone-viz included lablgtk, and a
Having some big problems using ViewMTN in FastCGI (and knowing pretty
much nothing about Python myself) I went on and made a smallish PHP
interface.
I wrote this scratch version in the last hour, it does pretty much
nothing except some rough equivalent of mtn log, it doesn't even have
a name yet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[sorry if this message is duplicated, but I don't see the first one on
mailing list, so I'm re-sending it]
Hi there.
I was thinking about using cvssync in a project of mine that
involves many CVS users (moreover most of them are non-programmers and
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there.
I was thinking about using cvssync in a project of mine that
involves many CVS users (moreover most of them are non-programmers and
I convinced them to use CVS only thanks to TortoiseCVS ^_^) but I
would like to use monotone nonetheless if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christof Petig wrote:
Is out there any documentation how to use it?
Look into monotone.texi within the branch
OK, I read it all. (well, I read 3.14, bit it seems to be the most of
the change isn't it?)
I figured most of that out with hep of monotone
It's been a while after I last were able to compile monotone on
cygwin, but being the error full of STL stuff and not having much time
to watch it closely, and having recently had some HDD corruption, I
put that apart with something like must be my STL with some files
corrupted.
But today I
Jon Bright wrote:
Lapo Luchini wrote:
AC_CACHE_CHECK([if this is Windows],
ac_win32, [
- AC_TRY_RUN([
-#ifdef WIN32
-#include windows.h
-int main(void)
-{
- return 0;
-}
-#else
-__wont_compile_
-#endif
-],
+ AC_TRY_COMPILE([#include windows.h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timothy Brownawell wrote:
A number of old revisions now have two sets of certs, one by
[EMAIL PROTECTED] (the certs you already had) and one by
[EMAIL PROTECTED] (the new certs).
Ah ok, I feared it was some kind of bug in which the certs didn't
Nathaniel Smith njs at pobox.com writes:
- Root dir renaming is now supported. See new commands
'pivot_root', 'merge_into_dir'.
- As a side-effect, it is not possible to run 'rosterify' on
histories in which two independent lines of history were
Whoops, I sync'ed with a laptop that had the quite old translations I
did some months ago... and now mtn merge say this:
monotone: [source] 597dfcb31c5f9f1835157f5bcf03273625bf235b
monotone: [source] c7db63267eaaa6718afacb1227f93323b53a4802
monotone: warning: rename target conflict: nodes 1500,
% mtn-0.25 sy
monotone: connessione a ‘motoko.lapo.it’
[...]
% mtn-0.26pre2+ sy
monotone: connecting to motoko.lapo.it
[...]
% ls -l /usr/share/locale/it/LC_MESSAGES/monotone.mo
-rw-r--r-- 1 lapo None 36646 Apr 1 13:26
/usr/share/locale/it/LC_MESSAGES/monotone.mo
...so why version 0.26 doesn't
Timothy Brownawell tbrownaw at gmail.com writes:
On Sat, 2006-04-01 at 13:47 +0200, Lapo Luchini wrote:
% mtn-0.25 sy
monotone: connessione a ‘motoko.lapo.it’
[...]
% mtn-0.26pre2+ sy
monotone: connecting to motoko.lapo.it
[...]
% ls -l /usr/share/locale/it/LC_MESSAGES
Another one of the questions that came to me while translating:
- many strings (e.g. branch '%s' is empty) talk about branches and
tags 'directly'
- many others (e.g. put a symbolic tag cert on a revision) talk
about 'cert branch' and 'cert tag', implying the user to know that
every one of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Levitte - VMS Whacker wrote:
If that's what I think it is, it's specific to these french
translations:
#: netsync.cc:708
msgid bytes in
msgstr octets $,1wi
#: netsync.cc:710
msgid bytes out
msgstr octets $,1wg
BTW:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
That would change the revision IDs again, woudn't it?
That's for sure: different hash algorithm, different hash value.
Or we could recognise both sets of revision IDs -- the old ones for
old revisions, the new ones for new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wim Oudshoorn wrote:
Question
Is there an efficient way to find this out?
mtn cat filename gives status 1 on error, else the file content.
But gettin' the whole content may be a bit overkill (exp. in cases of
big files) just to know if it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Patrin wrote:
On 4/12/06, Lapo Luchini [EMAIL PROTECTED] wrote: Wim Oudshoorn wrote:
Question Is there an efficient way to find this out?
mtn cat filename gives status 1 on error, else the file content.
But gettin' the whole
Is there a practical size limit to a versioned file?
A few scenarios come to my mind:
a. no limit: the file is read, elaborated, and put in database in chunks
or something like that
b. one copy: enough memory is needed to contain the whole file, but no
more copies are needed
c. a few copies: 2-3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Binary package is already available on Cygwin mirrors.
http://cygwin.com/ml/cygwin/2006-04/msg00378.html
The FreeBSD port is waiting for some confirmations, but should be
pretty close.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/95656
I'll be
Richard Levitte - VMS Whacker richard at levitte.org writes:
On the plus side, this also means that we could leave it to the user
to decide if and how strong compression xe wants. This means, of
course, the the peers in a netsync communication will have to do a bit
of negitiation at the
,quote(value) FROM revision_certs'
This does extract value in X'0123456789abcdef' format.
(even easier to use than base64, imho)
Lapo
--
Lapo Luchini
www.lapo.it
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Václav Haisman wrote:
The FreeBSD port is waiting for some confirmations, but should be
pretty close.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/95656
What's up with the update of monotone FreeBSD port? I am eagerly
waiting for it :)
It
if the code were committed to
some publicly reachable branch I'd for sure take at least a peek =)
I'll re-iterate my offer of push access to venge.net -- just send a
key whenever you'd like :-).
...or anywhere else, but just let us see it: the screenshot were
breathtaking ;-)
- --
Lapo Luchini
/i686-pc-cygwin/3.4.4/include/c++/ext/hashtable.h:518:
error: no match for call to `(const hashmap::hashu32) (const long
unsigned int)'
--
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
___
Monotone-devel mailing list
/
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJEgD7TAAoJELBiMTth2oCDQ0oP/2itc3iHc7LrZcJdr9WTTlLJ
t
easier
than beginning to dig in the source code, i.e. discovering the meaning
of single-letter-functions and so on, but the latter is the best thing
to do, and with today I'm beginning to do it ;-)
Lapo
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
Nathaniel Smith wrote:
ending in newlines is usually also a bug, and can be simply fixed.
In particular, arguments to P/L/W/N/E will all have a newline
appended automatically, and should not contain a literal trailing
)'
make[2]: *** [mtn-xdelta.o] Error 1
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJEgVC4AAoJELBiMTth2oCDz04P
from monotone ;)
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIbBAEBAgAGBQJEgWKfAAoJELBiMTth2oCDYeMP+J/h3/lK5Nz1P8hfcpqWepcH
behavior) is close to perfect or,
well... close to what I would like the feature to be. =)
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
xdelta.cc:88: instantiated from here
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/ext/hashtable.h:518:
error: no match for call to `(const hashmap::hashu32) (const long
unsigned int)' make[2]: *** [mtn-xdelta.o] Error 1
OK
a working cygwin installation.
I can provide all the know-how.
Ah, yes, and I *will* upgrade cygwin's official monotone package to
0.27 ASAP, should have done that already, but had a few busy evenings
at home.
Lapo
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ
him to ask for the status of his work
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJEmccIAAoJELBiMTth2oCDXU0P
remaining monotone reference I can see is maybe this one:
monotone.cc:635: F(monotone %s doesn't use the option %s)
that should probably changes to use %s as command name, too?
Lapo
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE
on
that bug states, there may be some locking problems... I'll investigate
further.
If anyone already did this work and solved the problem, please tell me
so ASAP ;-)
--
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
Yes, indeed seems that sqlite's os.h treats Cygwin as a WIN build
instead of a UNIX one.
Just removing the __CYGWIN__ case from sqlite/os.h seemed to resolve
the problem.
But the are locking issues indeed.
filemon's output
and, of course, the website states no slave.
I wonder why..?
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJEu
.serverkompetenz.net/trac/browser?branch=net.venge.monotone
Mhh, is this page meant to show mtn_benchmark stuff instead of
monotone sources themselves?
Lapo
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin
Graydon's signature through 7
different 4 people chains ;-)
text: http://tinyurl.com/nsuza
image: http://tinyurl.com/oagwr
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG
in it I did miss...
Lapo
--
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
Lapo Luchini wrote:
I was trying to cvs_import the while FreeBSD /src repository and I got a
std::bad_alloc.
I guess the problem is that some data is kept in RAM and swap file finished?
Yes, I guess that's so, because after a few minutes I got 311M of RES in
top, when the CLI showed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathaniel Smith wrote:
On Mon, Jul 31, 2006 at 09:07:58PM +0200, Lapo Luchini wrote:
I wonder: why the sources are only available as .tar.gz?
Using .tar.bz2 they compress down to 3.5 MiB instead of 4.6 MiB.
Tradition? (Does it matter?)
Well, it's
just to be sure the download wasn't corrupted.
But of course I'd prefer a digital signature from one of the
developers ;-)
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Dickinson wrote:
It seems that, at least on debian, gcc/g++ 3.4 isn't new enough to
get a working copy of monotone. Compiling with gcc/g++ 4.1 was
successful. I can provide more info and/or create a bug report if
necessary, but I wanted to
paths
...with the expected answer. Why was it in the first output at all, then?
--
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman
--
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
and probably more.
I also wonder how much difficult would be to have an incremental
cvs_import (to keep in sync at least in one direction).
Just wondering. I'll probably elaborate on it further as soon as I have
time to think about it further myself ;-)
--
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP
.
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJE7KLbAAoJELBiMTth2oCDwBYQAJgoCqO6jEBPXIVuoqYD5gTS
,
directory or filenames, they are stored only once).
In order to get rid of the extra file size you'd have to create a new
DB and locally sync the branches you're interested in into the new DB,
and then drop the old one.
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Dickinson wrote:
(Wouldn't that be better spelled as: $@ $TMPFILE? My shell
is a bit rusty.)
shift doesn't affect $@ that I can see (I did try that first).
It does, in fact:
% cat p.sh
#!/bin/sh
echo $1
shift
echo $@
% ./p.sh 1 2 3 4
1
the poll open for another few days, lets see where we come out...
Thomas.
1. monoto.ne
2. monotone.net (WHOIS: Status: Locked)
3. monotone-vcs.org
4. monotone.it (I could help registering it as an Italian domain)
5. monotone.ca
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it
mean as a pronounceable word, as a location it certainly is
somewhat representative of the creator's and some of the developers
place in the world)
Overall .net would be the best 1st level domain, being distributed
and all. But as far as I ounderstoo that would be a bit complicated.
- --
Lapo
FreeBSD's src CVSROOT:
% find . -type f | wc -l
62501
% du -hxs .
1,8G.
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
big different primes.
(and me not being a cryptographer I guess it would have other
problems anyway, but at least it wouldn't be weak to such
frequently-happening use cases ^_^)
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version
are Updated and translaetd a bit more (XX missing)) were really
necessary/useful...
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
, in the meantime I made revision
30f099d35c1a70af1c52ce8aeebb0037d66ae1e8 without a ChangeLog entry...
but if this gets official we may as well (only for consistency sake)
remove the old ones.
In that case I volunteer to do it ;-)
Lapo
- --
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it
) $(usher_LDADD) $(LIBS)
+ $(CXXLINK) $(usher_LDFLAGS) $(usher_OBJECTS) $(usher_LDADD)
$(LIBS) $(LIBINTL) $(LIBICONV)
mostlyclean-compile:
-rm -f *.$(OBJEXT)
--
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN
http://wikitest.freebsd.org/VersionControl
This page (and the linked ones) details the features that FreeBSD
requires (or would like to have) in its chosen successor of CVS.
It would be neat to be a candidate ;-)
Or, at the very least, it could be a list of interesting use cases...
--
Lapo
Lapo Luchini wrote:
http://wikitest.freebsd.org/VersionControl
My personal analysis of monotone vs wanted features (very rough):
VCSFeatureCVSImport: Ability to import entire current CVS repository,
including history
our cvs_import would almost suffice, branch reconstruction would be a
plus
It seems the process of open-sourcing Java JDK is leading Sun people to
choose a new VCS as well.
The choice seems to be going towards Mercurial, as past experience of
OpenSolaris (also Sun) chose to use in april 2006.
They don't seem to have definitely decided yet, though.
Mark Reinhold’s Other
Daniel Carosone wrote:
On Sun, Oct 01, 2006 at 03:54:39PM +0200, Lapo Luchini wrote:
mtn: fatal: std::logic_error: graph.cc:72: invariante 'I(!next.empty())'
violato
This ought to be fixed in mainline, with the change in revision
a:njs/d:2006-09-22T07:01:26 - please try
1 - 100 of 588 matches
Mail list logo
