* Zack Weinberg:
* pcre, idna: I'm not too sure about these, but dynamic linking seems
to make more sense. I didn't hit any stumbling block so far in nvm.stripped.
Concur. API/ABI stability shouldn't be an issue with these.
The PCRE C++ API/ABI is not stable, and the regexp syntax isn't,
* Thomas Keller:
There are two downsides, though: The first is that only HTML contents
can be tracked, but not individually downloaded files, since Google
only notices those contents from which the Javascript code is
executed, so afaik its not possible to generate download statistics
through
* Stephen Leake:
On the other hand, when using a pre-installed pcre library, apparently
pcre_config.h is _not_ available.
No, this is intentional. A library config.h files cannot be included
elsewhere because they conflict with the application config.h files.
* Nathaniel Smith:
PLEASE REPLY TO THIS EMAIL, CC'ING monotone-devel@nongnu.org, AND
SAY THAT YOU ARE FINE WITH YOUR CONTRIBUTIONS TO monotone.texi BEING
RELEASED UNDER THE GPL (v2 or later).
I'm fine with relicensing my (minor) contributions under the GNU GPL,
version 2 or later.
* Nathaniel J. Smith:
This is where key idea 2 comes in again. Let's define an
equivalence relation ~, as:
for all x and y that are not equal to #, x ~ y iff x = y.
for all x, # ~ x is always true.
Or in words: every normal value is similar to itself, plus, # is
similar to
* Nathaniel Smith:
mozilla : 36.9 MiB/s
openssl (no-asm debian-i386) : 56.5 MiB/s
openssl (no-asm debian-i386-i686/cmov) : 56.5 MiB/s
botan: 64.1 MiB/s
beecrypt (from debian) :
* Zack Weinberg:
Typical use case (from cmd_merging.cc - I'm not posting a diff for
that, as I have a lot of other changes in that file right now):
// Just pick some unused revid, all that's important is that it not
// match the work revision or any ancestors of the base
* Richard Levitte:
Wasn't it concluded that we (monotone ppl) would use the 0.25-0.x
standard, and that Debian maintainers would use 0.25-y, so there would
be a difference between us and Debian?
Yes, but this was an NMU on Debian's side, so the 0.25-0.x syntax is
strongly suggested. Perhaps
* Steven E. Harris:
I decided to ask here because the testing version is still at
0.19-1.
0.24-1 needs a new boost, which will hit testing later today. The
current monotone version will migrate to testing at the same time.
___
Monotone-devel
* Christof Petig:
My requirements are very simple: I need to attach a list of {CVS
revision per file} to an existing revision.
Do you need to attach this information to the *revision*, or to a
specific version of a file?
___
Monotone-devel mailing
* Bruno Hertz:
As a sidenote, this will happen more often as monotone becomes more
widespread, since ppl tend to be confused by tools which implement
their own globbing syntax (cf. 'find'). Especially so when it's
differing from shell semantics or limited to a subset of it.
Couldn't monotone
* Wim Oudshoorn:
All of them are expanded. It is obviously a problem with the msys
shell.
Not necessarily. On Windows, wildcard expansion is typically
performed by the application (or some kind of libc stub which
initializes the argv array).
___
* Nathaniel Smith:
Oh, sure, it's obviously waiting on IO. The question is what IO are
we doing that takes so long, and how can we not do that :-).
It's probably the effect of internal database fragmentation, coupled
with file system fragementation:
monotone.db: 8686 extents found,
* Richard Levitte:
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?
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
* Zbynek Winkler:
Has it been considered to let someone else do this work for monotone? I
think git is using cvsps [1] to import cvs repositories.
Does cvsps still open one connection per file and revision? That
behavior was rather antisocial.
* Jon Bright:
I also agree with this. For me,
568b-2462-456e-9a57-4326-93df-936d-4835
would be much more readable than
568b2462456e9a57432693df936d4835
Only the latter can be copied to the X selection with a single double
click. (BTW, that's the reason why I don't think long hashes are
* Eric Anderson:
Is .data() assumed to be contigous as well?
Yes. The difference to .c_str() is that the character array to which
a pointer is returned is not guaranteed to be NUL-terminated.
___
Monotone-devel mailing list
* Matthew A. Nicholson:
for REV in `monotone automate select b:OLDBRANCH`; do
yes PASSWORD | monotone cert $REV branch NEWBRANCH
done
That should keep you from having to enter the password for each cert
On multi-user machines, this is not a good idea because the command
line is a
* Nathaniel Smith:
Also, I'm going to assume that we don't support file suturing -- a
file is born exactly once, and in any particular downwards path
through the ancestry, dies exactly once or not at all.
With such a model, wouldn't it be easier to track file identity with
artificially
* Nathaniel Smith:
(One horrible idea I had, suitable for scaring small children who are
interested in merge algorithms: since it seem like trees may actually
be _easier_ to merge than text, by passing to the representation
of nodes-and-pointers-to-parents and then applying a nice scalar
* Nathaniel Smith:
Well, yes, it's good advice. But since M _cannot_ be a non-macro,
What is it doing, actually? Maybe there's a completely different way
to get things done.
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
* Nathaniel Smith:
When is venge.net switching to 0.20?
Just switched it over.
With monotone at manifest d538000d4a53ebe2c9b275cb30639aeba22f9e80, I
get the following error message when I try to run monotone pull:
monotone: warning: caught bad_decode exception decoding input from
peer
Florian Weimer schrieb:
With monotone at manifest d538000d4a53ebe2c9b275cb30639aeba22f9e80, I
get the following error message when I try to run monotone pull:
monotone: warning: caught bad_decode exception decoding input from
peer venge.net: 'bad checksum 0xde836079 vs. 0x122b5343'
Try
* Wim Oudshoorn:
However in that case lcad has a bug :-)
Consider the following graph:
A
/ \
B C
| /|
| / E
D |\
| F \
| | G
|
* Tomas Fasth:
But I don't have a better solution, either, because I can never
commit myself to a certain timeframe, especially not a tight one,
because of my own business, my wife and kids, and also the other
Debian packages I have to maintain (hm, just a few, really).
Maybe with a
* Matt Johnston:
If it'll fix dir dropping etc, sounds sane. Would this have
consequences for making the root directory renamable? I'd
like to seen renamable root directories eventually getting
supported, as it seems to provide a convenient way to bring
third party branches into a project
* Nathaniel Smith:
On Sun, May 01, 2005 at 06:51:54PM +0200, Florian Weimer wrote:
* Nathaniel Smith:
Fortunately, it seems like codeville-merge is a viable replacement
here (it can be applied to both content merges and tree rearrangement
merges), and with some recent improvements
* Richard Levitte:
In message [EMAIL PROTECTED] on Sun, 1 May 2005 00:29:48 -0700, Nathaniel
Smith [EMAIL PROTECTED] said:
njs Here's another pathological case for 3-way merge:
njsA
njs|
njsB
njs / \
njs C D
njs Suppose that a file was added on the A-B edge, and then
* Christof Petig:
Is
func((some_string+something).c_str())
guaranteed to work with every compiler.
Yes, deallocation of the temporary will be deferred to after the
evalation of the full expression.
And what are descriptors?
___
Monotone-devel
* Richard Levitte:
In message [EMAIL PROTECTED] on Mon, 18 Apr 2005 12:27:07 +0200, Florian
Weimer [EMAIL PROTECTED] said:
fw Would it be possible to include the diffs inline, and not as
fw attachments? In other words, Content-Disposition: inline
fw instead of Content-Disposition
* Bruce Stephens:
I think you're right that inventory would be more suited to listing
files that are in the repository (like monotone cat manifest but
without the hash, I guess).
Actually, it's called list known.
___
Monotone-devel mailing list
* Richard Levitte:
I was a bit clumsy in the way I wrote that. My question is, how do I
correctly detect a binary blob from text?
A few GNU tools use the presence of NUL characters to identify binary
files (some of them only in the first few K of the file, AFAIK).
32 matches
Mail list logo
