On Thu, Jul 07, 2005 at 12:53:54PM -0700, Shaun Jackman wrote:
> In the following dialog, why is 'monotone status configure.ac' giving
> the status of both files?
I don't know; it seems wrong to me. I tried reproducing it here with
0.20, but it worked fine; maybe it'd be possible to provide more
On Thu, Jul 07, 2005 at 08:09:09PM +0200, Vaclav Haisman wrote:
>
> I need more to be able to do make check. Patch attached.
Thanks. Applied to mainline.
-- Nathaniel
--
Damn the Solar System. Bad light; planets too distant; pestered with
comets; feeble contrivance; could make a better one m
On Fri, Jul 08, 2005 at 12:04:32AM -0400, Nathan Cournia wrote:
> I think I may have found my problem. It appears the binary I
> downloaded somehow was corrupted (bunzip2 didn't complain though).
> The corrupted binary has a MD5 sum of:
>
> $ md5sum monotone-0.20-linux-x86
> 1447237be23f234a088c
I think I may have found my problem. It appears the binary I
downloaded somehow was corrupted (bunzip2 didn't complain though).
The corrupted binary has a MD5 sum of:
$ md5sum monotone-0.20-linux-x86
1447237be23f234a088cb6f08adc38ea monotone-0.20-linux-x86
while the binary I redownloaded has a
As a follow-up to my previous message. I tried syncing again, and got
the same result. The debug log should be attached.
nathan
debug2
Description: Binary data
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/
On Thu, Jul 07, 2005 at 06:25:16PM +0200, Florian Weimer wrote:
> > 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 de
On Thu, Jul 07, 2005 at 11:47:29AM +0200, Peter Simons wrote:
> Nathaniel Smith writes:
>
> >> | pull [ADDRESS[:PORTNUMBER] [PATTERN]]
>
> > It's a shell pattern. (It was a regex for a while during
> > development, so it's an outdated message.)
>
> One feature I depended on is the ability t
In the following dialog, why is 'monotone status configure.ac' giving
the status of both files?
Cheers,
Shaun
$ monotone diff | diffstat
ChangeLog |4 +
configure.ac|2
$ monotone status ChangeLog
new_manifest [bda98ec05ff89b94a6db52241704675d5ee5a715]
old_revision [8a60d3f99a
I need more to be able to do make check. Patch attached.
VH
On Thu, 7 Jul 2005, Vaclav Haisman wrote:
> This was meant to go to the list, not just Nathaniel.
>
> -- Forwarded message --
> Date: Thu, 7 Jul 2005 19:07:25 +0200 (CEST)
> From: Vaclav Haisman <[EMAIL PROTECTED]>
> T
This was meant to go to the list, not just Nathaniel.
-- Forwarded message --
Date: Thu, 7 Jul 2005 19:07:25 +0200 (CEST)
From: Vaclav Haisman <[EMAIL PROTECTED]>
To: Nathaniel Smith <[EMAIL PROTECTED]>
Subject: Re: [Monotone-devel] ANNOUNCE: monotone 0.20
I had to use the attach
On Thu, 2005-07-07 at 11:25 -0500, Brian Downing wrote:
> On Thu, Jul 07, 2005 at 10:17:58AM -0500, Timothy Brownawell wrote:
> > > With (Boost's) regular expressions, I could say
> > >
> > > foo\.(?!bar)\.*
> > >
> > > to match, say "foo.abc", but not "foo.bar". How do I do this
> > > with she
> 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. 0x122b53
Christof Petig schrieb:
>>Just a heads up: This also occurs under Ubuntu/breezy on amd64 (g++
>>4.0.0, Boost 1.32) with both 0.20 and HEAD.
>
>
> And different Optimization levels do not change anything (-O0 also errors).
make CXXFLAGS="-O2 -fno-strict-aliasing \
-DBOOST_REGEX_V4_CHAR_REGEX_TRAI
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'
Tr
On Thu, Jul 07, 2005 at 10:17:58AM -0500, Timothy Brownawell wrote:
> > With (Boost's) regular expressions, I could say
> >
> > foo\.(?!bar)\.*
> >
> > to match, say "foo.abc", but not "foo.bar". How do I do this
> > with shell patterns now?
>
> I don't think you can. There seems to be some co
Timothy Brownawell wrote:
On Thu, 2005-07-07 at 11:47 +0200, Peter Simons wrote:
Nathaniel Smith writes:
>> | pull [ADDRESS[:PORTNUMBER] [PATTERN]]
> It's a shell pattern. (It was a regex for a while during
> development, so it's an outdated message.)
One feature I depended on is the abili
Christof Petig wrote:
> Christof Petig schrieb:
>>>I saw this too, but it seemed only to occur with particular
>>>compiler optimisation flags. As a workaround I just
>>>commented out the bulk of
>>>/usr/include/boost/regex/v4/char_regex_traits.hpp in the
>>>"deprecated" namespace, and it compiled f
Christof Petig schrieb:
>>I saw this too, but it seemed only to occur with particular
>>compiler optimisation flags. As a workaround I just
>>commented out the bulk of
>>/usr/include/boost/regex/v4/char_regex_traits.hpp in the
>>"deprecated" namespace, and it compiled fine.
>>
>>Given monotone com
Matt Johnston schrieb:
>>/usr/include/boost/regex/v4/char_regex_traits.hpp: In member function
>>'uint_fast32_t
>>boost::deprecated::char_regex_traits_i::lookup_classname(const
>>wchar_t*, const wchar_t*) const':
>>/usr/include/boost/regex/v4/char_regex_traits.hpp:68: error:
>>'boost::re_detail::c
On Thu, 2005-07-07 at 11:47 +0200, Peter Simons wrote:
> Nathaniel Smith writes:
>
> >> | pull [ADDRESS[:PORTNUMBER] [PATTERN]]
>
> > It's a shell pattern. (It was a regex for a while during
> > development, so it's an outdated message.)
>
> One feature I depended on is the ability to negat
On Mon, Jul 04, 2005 at 05:54:21PM -0400, Hendrik Boom wrote:
> On Mon, Jul 04, 2005 at 12:36:43AM -0700, Nathaniel Smith wrote:
> > On Sun, Jul 03, 2005 at 09:28:53PM -0400, Hendrik Boom wrote:
> > > It told me to send this to you. The monotone I am using is the one
> > > distributed with sarge.
Nathaniel Smith writes:
>> | pull [ADDRESS[:PORTNUMBER] [PATTERN]]
> It's a shell pattern. (It was a regex for a while during
> development, so it's an outdated message.)
One feature I depended on is the ability to negate matches.
With (Boost's) regular expressions, I could say
foo\.(?!b
* 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 v
On 7 jul 2005, at 7:17, Nathaniel Smith wrote:
Because monotone's philosophy is to defer trust checking to individual
users; so netsync just shuffles information around, so that people
will have the appropriate information available to make their own
decisions. So it doesn't check certs or do an
24 matches
Mail list logo
