Re: Release rules Was: Re: [Monotone-devel] conflicts store vs show_conflicts

2010-11-25 Thread Richard Levitte
In message 4ced08f9.1040...@bluegap.ch on Wed, 24 Nov 2010 13:45:45 +0100, Markus Wanner mar...@bluegap.ch said: markus (After all, who's going to trust a revision control system markus that doesn't even get its own versioning correct?) Oh, I just have to pick on this one: revisions and

Re: Release rules Was: Re: [Monotone-devel] conflicts store vs show_conflicts

2010-11-25 Thread Richard Levitte
In message 4ced08f9.1040...@bluegap.ch on Wed, 24 Nov 2010 13:45:45 +0100, Markus Wanner mar...@bluegap.ch said: markus For monotone, we had netsync flag days, which represent full markus incompatibilities (can't speak to each other). Then we also had database markus migrations, where a one-way

Re: [Monotone-devel] Usher and older installations...

2010-11-25 Thread Richard Levitte
Actually, never mind that. A little more mind twisting and I got how to do this: server .catchall. pattern local --confdir=/etc/monotone --db=/var/lib/monotone/default.mtn --no-standard-rcfiles --rcfile=/etc/monotone/hooks.lua --keydir=/var/lib/monotone/keys It plays perfectly together

[Monotone-devel] Re: Release rules Was: Re: conflicts store vs show_conflicts

2010-11-25 Thread Lapo Luchini
Markus Wanner wrote: Then we also had database migrations, where a one-way upgarde is possible, but not backwards. Well, not exactly. I did (manually) downgrade a database, one time. =) -- Lapo Luchini - http://lapo.it/ ___ Monotone-devel mailing

Re: Release rules Was: Re: [Monotone-devel] conflicts store vs show_conflicts

2010-11-25 Thread Markus Wanner
On 11/24/2010 09:54 PM, Richard Levitte wrote: Oh, I just have to pick on this one: revisions and versions aren't the same thing... Okay, then let's talk about VCSes.. ;-) Regards Markus ___ Monotone-devel mailing list Monotone-devel@nongnu.org

Re: Release rules Was: Re: [Monotone-devel] conflicts store vs show_conflicts

2010-11-25 Thread Markus Wanner
On 11/24/2010 09:56 PM, Richard Levitte wrote: 0.99 is different enough from 0.48 to deserve being the upcoming 1.0, Huh? I'm sorry if that's ignorant, but I didn't realize any change in 0.99, except for it being slower, but less annoying with the commit message editor than 0.48. there are

[Monotone-devel] Re: Release rules Was: Re: conflicts store vs show_conflicts

2010-11-25 Thread Lapo Luchini
Markus Wanner wrote: On 11/24/2010 09:56 PM, Richard Levitte wrote: 0.99 is different enough from 0.48 to deserve being the upcoming 1.0, Huh? I'm sorry if that's ignorant, but I didn't realize any change in 0.99, except for it being slower, but less annoying with the commit message editor

Re: [Monotone-devel] Re: Release rules Was: Re: conflicts store vs show_conflicts

2010-11-25 Thread Markus Wanner
On 11/25/2010 06:10 PM, Lapo Luchini wrote: Well, for me 0.47→0.99 had the *incompatibility* you are talking about, in the instance of the changed method to synchronize with server which needed a change of habits from: mtn sy lapo.it 'it.*' to mtn sy 'mtn://lapo.it/?it.*' IIRC the

[Monotone-devel] Recruiting and Planning

2010-11-25 Thread Thomas Keller
Hi all! I have a bit the impression that bigger parts of our community are in suspend mode (beside a few usual suspects) and because I don't want to see you all go hibernating soon, here is a deal: 1) we need more people, especially somebody for design (site, ci, documents, etc.) and