[Monotone-devel] Usher difficulties

2006-04-10 Thread Ethan Blanton
First, usher has not been updated to exec 'mtn' by default rather than 'monotone'; this is not a big deal to work around (usher -m mtn), but the default should probably be changed. A trivial patch is attached. Second, with both the usher from 0.26-pre3 and the usher from 0.26 as released, I am ha

Re: [Monotone-devel] Usher difficulties

2006-04-10 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Mon, 10 Apr 2006 09:48:49 -0400, Ethan Blanton <[EMAIL PROTECTED]> said: eblanton> First, usher has not been updated to exec 'mtn' by default eblanton> rather than 'monotone'; this is not a big deal to work eblanton> around (usher -m mtn), but the default should

Re: [Monotone-devel] Usher difficulties

2006-04-10 Thread Ethan Blanton
Richard Levitte - VMS Whacker spake unto us the following wisdom: > In message <[EMAIL PROTECTED]> on Mon, 10 Apr 2006 09:48:49 -0400, Ethan > Blanton <[EMAIL PROTECTED]> said: > eblanton> First, usher has not been updated to exec 'mtn' by default > eblanton> rather than 'monotone'; this is not a

[Monotone-devel] Rosterify and certificate keys

2006-04-10 Thread Tom Koelman
Hi, I just rosterified a database. On inspecting the contents of the new database I found out that all certificates had been reissued with my own e-mail-adress. This would be an issue for a trust model based on who handed out what certificate. Is there some way in which I can make the certificate

[Monotone-devel] Re: Rosterify and certificate keys

2006-04-10 Thread Bruce Stephens
Tom Koelman <[EMAIL PROTECTED]> writes: > I just rosterified a database. On inspecting the contents of the new > database I found out that all certificates had been reissued with my > own e-mail-adress. This would be an issue for a trust model based on > who handed out what certificate. Yes indee

Re: [Monotone-devel] Rosterify and certificate keys

2006-04-10 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Mon, 10 Apr 2006 17:25:56 +0200, Tom Koelman <[EMAIL PROTECTED]> said: tkoelman> Another thing I noticed is that, understandably, all tkoelman> revision hashes have changed. This has the unfortunate side tkoelman> effect that propage Changelog entries make no sen

Re: [Monotone-devel] Rosterify and certificate keys

2006-04-10 Thread Joel Crisp
Hi Richard I think you might have missed the point slightly...If I understand this correctly, he made the changelog in the past incorporating reversion hashes which have now changed due to the 'rostification' of the databaseso the historical fact is that he HAS written down specific hashes

[Monotone-devel] Re: Can anyone check for the old ipv6 bug?

2006-04-10 Thread Henry Nestler
Richard Levitte - VMS Whacker schrieb: In message <[EMAIL PROTECTED]> on Fri, 07 Apr 2006 15:49:46 +0200, Henry Nestler <[EMAIL PROTECTED]> said: Henry.Ne> I'm use unchanged binary from Henry.Ne> http://www.venge.net/monotone/downloads/mtn-0.26pre3-linux-x86.bz2 Henry.Ne> Henry.Ne> Running: H

Re: [Monotone-devel] Rosterify and certificate keys

2006-04-10 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Mon, 10 Apr 2006 22:36:44 +0100, Joel Crisp <[EMAIL PROTECTED]> said: jcrisp> I think you might have missed the point slightly...If I jcrisp> understand this correctly, he made the changelog in the past jcrisp> incorporating reversion hashes which have now change

Re: [Monotone-devel] Rosterify and certificate keys

2006-04-10 Thread Joel Crisp
Yeah, I was talking about the manually generated changelogs. ;-) Joel Richard Levitte - VMS Whacker wrote: In message <[EMAIL PROTECTED]> on Mon, 10 Apr 2006 22:36:44 +0100, Joel Crisp <[EMAIL PROTECTED]> said: jcrisp> I think you might have missed the point slightly...If I jcrisp> understan

[Monotone-devel] Re: Can anyone check for the old ipv6 bug?

2006-04-10 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Mon, 10 Apr 2006 23:43:26 +0200, Henry Nestler <[EMAIL PROTECTED]> said: Henry.Ne> Richard Levitte - VMS Whacker schrieb: Henry.Ne> > In message <[EMAIL PROTECTED]> on Fri, 07 Apr 2006 15:49:46 +0200, Henry Nestler <[EMAIL PROTECTED]> said: Henry.Ne> > Henry.Ne

[Monotone-devel] Re: Can anyone check for the old ipv6 bug?

2006-04-10 Thread Henry Nestler
Richard Levitte - VMS Whacker wrote: Henry.Ne> + ./mtn-0.26-linux-x86 --debug --db=colinux-testing-run.db --norc Henry.Ne> --rcfile=serv_anonymous.lua --bind=66.36.228.15:5 serve '*' Henry.Ne> ... Henry.Ne> mtn-0: network error: name resolution failure for 66.36.228.15: Bad Henry.Ne> value

[Monotone-devel] Re: Can anyone check for the old ipv6 bug?

2006-04-10 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Tue, 11 Apr 2006 00:29:25 +0200, Henry Nestler <[EMAIL PROTECTED]> said: Henry.Ne> I'm ask again: Henry.Ne> Why not ships the quasistatic (Moschny) as linux binary? I have no idea what that is. Cheers, Richard - Please consider sponsoring my work on free s

[Monotone-devel] Coders are getting sloppy!

2006-04-10 Thread Richard Levitte - VMS Whacker
I'm noticing a disturbing lack of coder discipline, there's been a lot of changes lately that doesn't heed the following line from HACKING: All changes to the monotone source require an accompanying ChangeLog entry. It may be that you feel it's unnecessary, since your entry is normally simply c

[Monotone-devel] Re: Can anyone check for the old ipv6 bug?

2006-04-10 Thread Henry Nestler
Richard Levitte - VMS Whacker wrote: In message <[EMAIL PROTECTED]> on Tue, 11 Apr 2006 00:29:25 +0200, Henry Nestler <[EMAIL PROTECTED]> said: Henry.Ne> I'm ask again: Henry.Ne> Why not ships the quasistatic (Moschny) as linux binary? I have no idea what that is. http://www.ipd.uni-karlsruh

[Monotone-devel] Re: Coders are getting sloppy!

2006-04-10 Thread Henry Nestler
Hello Richard, All changes to the monotone source require an accompanying ChangeLog entry. In this case I have a small question. Often I need a merge after commit. My merge tool is xxdiff. I can only give *my* Changelog or the *other* as merged. I'm would like not lose from others and

[Monotone-devel] merge.ChangeLog, specialized ChangeLog merger

2006-04-10 Thread Timothy Brownawell
I have a specialized ChangeLog merger at https://netfiles.uiuc.edu/brownawe/www/merge.ChangeLog/ . It makes some assumptions (mostly, that entries are unique and don't change very much), but seems to work ok. Those of you getting this through monotone-devel may be interested in merge.ChangeLog.m

Re: [Monotone-devel] Rosterify and certificate keys

2006-04-10 Thread Daniel Carosone
On Mon, Apr 10, 2006 at 11:09:11PM +0200, Richard Levitte - VMS Whacker wrote: > The revs in the merge and propagate changelogs are really > irrelevant, the ancestors of the merge/propagate are registered > separately, and are always correct. The direct ancestors being merged may be, but the cho

Re: [Monotone-devel] Re: Coders are getting sloppy!

2006-04-10 Thread Nathaniel Smith
On Tue, Apr 11, 2006 at 01:53:11AM +0200, Henry Nestler wrote: > Often I need a merge after commit. My merge tool is xxdiff. I can only > give *my* Changelog or the *other* as merged. I'm would like not lose > from others and let falling down my Changes. Then I do a new commit for > the Chan

Re: [Monotone-devel] automate inventory

2006-04-10 Thread Glen Ditchfield
On Sunday 09 April 2006 23:53, Derek Scherger wrote: > Is anyone actually using inventory in its current form? I use it to deduce what files have been moved and renamed in maildirs. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lis