They have more up to date windows SDK headers also.
On Mon, Feb 3, 2014 at 7:01 AM, Stephen Leake
wrote:
> Markus Wanner writes:
>
>> On 02/02/2014 11:17 PM, Stephen Leake wrote:
>>> Although it appears we should switch to MinGW-w64, I think that can
>>> wait for the next release.
>>
>> Does "sw
Markus Wanner writes:
> On 02/02/2014 11:17 PM, Stephen Leake wrote:
>> Although it appears we should switch to MinGW-w64, I think that can
>> wait for the next release.
>
> Does "switch" here refer to the build we provide?
Yes.
> Or does it imply we
> have compilation issues, there? Did you t
On 02/02/2014 11:17 PM, Stephen Leake wrote:
> Although it appears we should switch to MinGW-w64, I think that can
> wait for the next release.
Does "switch" here refer to the build we provide? Or does it imply we
have compilation issues, there? Did you test MinGW-64?
Regards
Markus Wanner
s
Markus Wanner writes:
> I'm still interested in compiling a release.
Thanks for working on this.
> To my current knowledge, we are doing fine on Debian and Cygwin,
Windows (Mingw 32) is also fine.
Although it appears we should switch to MinGW-w64, I think that can
wait for the next release.
Hi,
I'm still interested in compiling a release. To my current knowledge, we
are doing fine on Debian and Cygwin, but currently have issues on
FreeBSD (10, at least) as well as OSX. I consider both to be things we
should fix before releasing a 1.1.
Regards
Markus Wanner
signature.asc
Descript
On 9/23/13 12:20 PM, Markus Wanner wrote:
On 09/11/2013 07:13 PM, Jeff Rizzo wrote:
Any chance of getting a new release this year? At the very least,
pkgsrc (pkgsrc.org) is having trouble because of building with Lua 5.2,
and it would be nice to have an actual release to deal with it.
Can you
On 09/11/2013 07:13 PM, Jeff Rizzo wrote:
> Any chance of getting a new release this year? At the very least,
> pkgsrc (pkgsrc.org) is having trouble because of building with Lua 5.2,
> and it would be nice to have an actual release to deal with it.
Can you please try rev fe1180f754da5d552c308b61
Any chance of getting a new release this year? At the very least,
pkgsrc (pkgsrc.org) is having trouble because of building with Lua 5.2,
and it would be nice to have an actual release to deal with it.
+j
___
Monotone-devel mailing list
Monotone-de
Am Tue, 22 Mar 2011 11:54:17 +0100
schrieb Thomas Keller :
> Am 13.03.2011 10:28, schrieb CooSoft Support:
> >Good point. It does seem a little bit 'odd' that a Gtk tool has a
> > dependency on KDE. So unless anyone has any objections, I'll switch
> > to meld. Remember that this setting just
Am 13.03.2011 10:28, schrieb CooSoft Support:
>I was thinking of switching the external comparison tool over to
> kdiff3 to match with the recommended merge tool for monotone but
> unfortunately that also suffers from the KDE dependency thing (as you
> would expect).
Since one can configure th
Stephen Leake writes:
> Richard Levitte writes:
>
>> In message <8262rpzyhw.fsf...@stephe-leake.org> on Fri, 11 Mar 2011 06:29:31
>> -0500, Stephen Leake said:
>>
>> stephen_leake> Stephen Leake writes:
>> stephen_leake>
>> stephen_leake> > I'm starting ... 'make distcheck' on Debian;
>> st
Richard Levitte writes:
> In message <8262rpzyhw.fsf...@stephe-leake.org> on Fri, 11 Mar 2011 06:29:31
> -0500, Stephen Leake said:
>
> stephen_leake> Stephen Leake writes:
> stephen_leake>
> stephen_leake> > I'm starting ... 'make distcheck' on Debian;
> stephen_leake>
> stephen_leake> Thi
Excellent - Many thanks for that Thomas :-)
I was thinking of switching the external comparison tool over to
kdiff3 to match with the recommended merge tool for monotone but
unfortunately that also suffers from the KDE dependency thing (as you
would expect).
Good point. It does seem
Am Sat, 05 Mar 2011 15:05:01 +
schrieb CooSoft Support :
> Just a quick email to announce the release of the above software
> on source forge and CPAN respectively.
>
> Basically the main work was to get these packages working with
> version 0.99.1 of Monotone.
>
> Monotone Brow
Richard Levitte writes:
> In message <8262rpzyhw.fsf...@stephe-leake.org> on Fri, 11 Mar 2011 06:29:31
> -0500, Stephen Leake said:
>
> stephen_leake> Stephen Leake writes:
> stephen_leake>
> stephen_leake> > I'm starting ... 'make distcheck' on Debian;
> stephen_leake>
> stephen_leake> Thi
Stephen Leake writes:
> Cygwin after that.
all : pass
check : extra/bash_completion fails, rest pass
doc/monotone.pdf : fails
cp: cannot create regular file `/figures/branch-heads.pdf': No such file or
directory
doc/monotone.ps : fails
make[1]: pdftops: Command not found
--
-- Stephe
__
In message <8262rpzyhw.fsf...@stephe-leake.org> on Fri, 11 Mar 2011 06:29:31
-0500, Stephen Leake said:
stephen_leake> Stephen Leake writes:
stephen_leake>
stephen_leake> > I'm starting ... 'make distcheck' on Debian;
stephen_leake>
stephen_leake> This is failing with:
stephen_leake>
stephe
Stephen Leake writes:
> I'm starting 'make check' now on MinGW
Failing on extra/*; rest pass
Other targets:
all : pass
win32-installer : pass
--
-- Stephe
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/l
Stephen Leake writes:
> Stephen Leake writes:
>
>> I'm starting ... 'make distcheck' on Debian;
>
> This is failing with:
>
> monotone-ciabot.py does not support --help
> monotone-ciabot.py does not support --version
>
>
> Apparently distcheck verifies that installed executables support
> stand
Stephen Leake writes:
> I'm starting ... 'make distcheck' on Debian;
This is failing with:
monotone-ciabot.py does not support --help
monotone-ciabot.py does not support --version
Apparently distcheck verifies that installed executables support
standard options.
--
-- Stephe
_
Am 05.03.11 16:05, schrieb CooSoft Support:
>Just a quick email to announce the release of the above software on
> source forge and CPAN respectively.
>
>Basically the main work was to get these packages working with
> version 0.99.1 of Monotone.
>
>Monotone Browser, not only having t
Just a quick email to announce the release of the above software on
source forge and CPAN respectively.
Basically the main work was to get these packages working with
version 0.99.1 of Monotone.
Monotone Browser, not only having the new selectors introduced in
0.99.1, also now has t
Am 04.12.10 13:21, schrieb CooSoft Support:
>Just to say that release 0.10 of Monotone::AutomateStdio that
> supports Monotone 0.99.1 is now available for download at:
>
>http://search.cpan.org/perldoc?Monotone::AutomateStdio
>
>For those mtn-browse users amongst you, you can simp
Just to say that release 0.10 of Monotone::AutomateStdio that
supports Monotone 0.99.1 is now available for download at:
http://search.cpan.org/perldoc?Monotone::AutomateStdio
For those mtn-browse users amongst you, you can simply untar the
package and drop the contents of the lib
Am 29.10.10 19:25, schrieb Markus Wanner:
> On 10/29/2010 02:19 PM, Stephen Leake wrote:
>> Thomas Keller writes:
>>
>>> Unfortunately some last minute changes make this release break on x86_64
>>> ..
>>> My apologies, we'll put out a new release shortly.
>
> Let me guess: version 0.99.9?
No, 0.
Am 29.10.10 14:19, schrieb Stephen Leake:
> Thomas Keller writes:
>
>> Unfortunately some last minute changes make this release break on x86_64
>
> We had a similar problem with the 0.48 release; the Win32 package did
> not build properly.
>
> I think we need to do a better job of being sure ev
On 10/29/2010 02:19 PM, Stephen Leake wrote:
> Thomas Keller writes:
>
>> Unfortunately some last minute changes make this release break on x86_64
>> ..
>> My apologies, we'll put out a new release shortly.
Let me guess: version 0.99.9?
> I think we need to do a better job of being sure everyth
Thomas Keller writes:
> Unfortunately some last minute changes make this release break on x86_64
We had a similar problem with the 0.48 release; the Win32 package did
not build properly.
I think we need to do a better job of being sure everything is tested
before a release.
That used to be acc
Am 11.09.10 18:06, schrieb CooSoft Support:
>Just to let you know the above version of mtn-browse has just been
> released and provides support for mtn version 0.48 (supports changes
> made to the diff output) and has a few minor bug fixes.
>
>You can download and look at the release notes
Just to let you know the above version of mtn-browse has just been
released and provides support for mtn version 0.48 (supports changes
made to the diff output) and has a few minor bug fixes.
You can download and look at the release notes/news from here:
http://sourceforge.net/pro
Hello Philipp,
The README file contains a list of all the dependencies required. I
don't know about Gentoo but all of the listed dependencies can be found
on CPAN (http://www.cpan.org/). They may also be hosted elsewhere (as in
your glib example) but you will find them all on CPAN as wel
On 31.05.2010 19:43, Anthony Edward Cooper wrote:
> I would like to announce the 0.70 release of mtn-browse:
I tried to compile this one here, and it states
> Can't locate Glib.pm in @INC ...
As I don't have the slightest clue about Perl, I can only guess that it
is "dev-perl/glib-perl" (from htt
I would like to announce the 0.70 release of mtn-browse:
Monotone browser (mtn-browse) is an application for browsing
Monotone VCS databases without the need for a workspace. The interface
allows one to:
* Easily select a revision from within a branch
* Find a revision using compl
On Thu, May 27, 2010 at 9:54 AM, Derek Scherger wrote:
> As I've announced earlier I'd like to start the machinery for the next
>> monotone release now that the database management branch has landed. So
>> if you have anything you'd also really like to see in the next monotone
>> version, please
One slight deviating point about breaking BC with au stdio... I feel
what ever applications we provide that use it should strive to cope with
BC breakages. E.g. Monotone:AutomateStdio works from 0.35 to the current
release as does mtn-browse which relies on it.
Hopefully though with the change
Philipp Gröschler wrote:
On 28.05.2010 10:23, CooSoft Support wrote:
I couldn't agree more with Thomas's point about Monotone dying if we are
not careful. It's a psychological thing. `Oh it's only at 0.xxx - still
unstable'.
Sure it's psychological and nowadays in the age of OSS, versi
Thomas Keller wrote:
Am 28.05.2010 15:07, schrieb Philipp Gröschler:
On 28.05.2010 10:23, CooSoft Support wrote:
I couldn't agree more with Thomas's point about Monotone dying if we are
not careful. It's a psychological thing. `Oh it's only at 0.xxx - still
unstable'.
Sure it's
Derek Scherger spake unto us the following wisdom:
> > 1) if a release only consists of bug fixes or has small, not BC-breaking
> > improvements (esp. in respect to automate), raise the patch release
> >
> > 2) if a release has bigger improvements or breaks BC, raise the minor
> > version
> >
> > 3
On Fri, May 28, 2010 at 1:30 AM, Thomas Keller wrote:
> I agree that continueing the current versioning scheme, just with a
> prefixed "1.", won't make much sense any longer, but I'm against
> complicating this too much. A new easy rule for now could be:
>
> 1) if a release only consists of bug f
Am 28.05.2010 15:07, schrieb Philipp Gröschler:
> On 28.05.2010 10:23, CooSoft Support wrote:
>> I couldn't agree more with Thomas's point about Monotone dying if we are
>> not careful. It's a psychological thing. `Oh it's only at 0.xxx - still
>> unstable'.
>
> Sure it's psychological and nowaday
Thomas Keller writes:
> After all we should all agree that monotone has been proven stable for
> many, many versions now and that we (the original and today's
> developers) should be proud of it, so proud that we should dare to put a
> proper version label on this darn thing.
+2 :).
>> BTW, a m
On 28.05.2010 10:23, CooSoft Support wrote:
> I couldn't agree more with Thomas's point about Monotone dying if we are
> not careful. It's a psychological thing. `Oh it's only at 0.xxx - still
> unstable'.
Sure it's psychological and nowadays in the age of OSS, versioning
schemes or rather the pro
CooSoft Support writes:
> I looked at the release
> notes and documentation regarding au stdio changes and read up on the
> new update command. Virtually all other au commands if not all simply
> mention what comes out on stdout by implication (apart from the
> barfing to stderr and exiting on er
I couldn't agree more with Thomas's point about Monotone dying if we are
not careful. It's a psychological thing. `Oh it's only at 0.xxx - still
unstable'. We have all done that at some point when looking at rival
projects as an end user in a hurry to get something up and running. It's
only if
Am 27.05.2010 18:54, schrieb Jack Lloyd:
> On Thu, May 27, 2010 at 09:38:32AM +0200, Thomas Keller wrote:
>
>> Apropos release - a fellow developer reminded me that we *might* want to
>> set a proper release number for the next release (you know what I'm
>> talking about, 1.0...) - given the fact
On Thu, 2010-05-27 at 18:47 -0500, Timothy Brownawell wrote:
> Is that a reasonable timeframe for a major version change, or are
> they
> supposed to last longer than that?
I say, make your own time table. If you want to release a new major
version every three months, that's fine with me. The mai
On 05/27/2010 06:08 PM, Jack Lloyd wrote:
On Fri, May 28, 2010 at 12:26:22AM +0200, Zbigniew Zag??rski wrote:
Hi,
2010/5/27 Jack Lloyd
I can think of a few things that might potentially happen that might
be harder to pull off post-1.0:
??- s/netxx/asio/
AFAIR, it's only implementation detai
On Fri, May 28, 2010 at 12:26:22AM +0200, Zbigniew Zag??rski wrote:
> Hi,
>
> 2010/5/27 Jack Lloyd
> > I can think of a few things that might potentially happen that might
> > be harder to pull off post-1.0:
> >
> > ??- s/netxx/asio/
>
> AFAIR, it's only implementation detail. Do we wan't to cha
Hi,
2010/5/27 Jack Lloyd
> I can think of a few things that might potentially happen that might
> be harder to pull off post-1.0:
>
> - s/netxx/asio/
AFAIR, it's only implementation detail. Do we wan't to change netsync
protocol together with asio introduction ?
> - netsync over TLS
It's a
Thomas Keller wrote:
Am 27.05.2010 12:56, schrieb Stephen Leake:
Thomas Keller writes:
Am 27.05.2010 10:22, schrieb CooSoft Support:
Sounds like a great idea to me, especially the 1.0 bit :-)).
However one minor point about the impending release (what ever
version it ma
On Thu, 2010-05-27 at 12:54 -0400, Jack Lloyd wrote:
> While 1.0 is good for a public image perspective, is it something that
> you want to lock yourself into?
As an user of Monotone, I would just like to mention my thoughts. I'd
prefer a move to the major.minor.patch model, with some clear rules
On Thu, May 27, 2010 at 09:38:32AM +0200, Thomas Keller wrote:
> Apropos release - a fellow developer reminded me that we *might* want to
> set a proper release number for the next release (you know what I'm
> talking about, 1.0...) - given the fact that we're still recognized as
> "alpha" softwar
On Thu, May 27, 2010 at 1:38 AM, Thomas Keller wrote:
>
> Hi all!
>
> As I've announced earlier I'd like to start the machinery for the next
> monotone release now that the database management branch has landed. So
> if you have anything you'd also really like to see in the next monotone
> versio
Am 27.05.2010 12:56, schrieb Stephen Leake:
> Thomas Keller writes:
>
>> Am 27.05.2010 10:22, schrieb CooSoft Support:
>>>Sounds like a great idea to me, especially the 1.0 bit :-)).
>>>
>>>However one minor point about the impending release (what ever
>>> version it may be) :-(...
>>>
>>
Thomas Keller writes:
> Am 27.05.2010 10:22, schrieb CooSoft Support:
>>Sounds like a great idea to me, especially the 1.0 bit :-)).
>>
>>However one minor point about the impending release (what ever
>> version it may be) :-(...
>>
>>I was looking at the changes for the next releas
Am 27.05.2010 10:22, schrieb CooSoft Support:
>Sounds like a great idea to me, especially the 1.0 bit :-)).
>
>However one minor point about the impending release (what ever
> version it may be) :-(...
>
>I was looking at the changes for the next release and noticed the au
> update co
Sounds like a great idea to me, especially the 1.0 bit :-)).
However one minor point about the impending release (what ever
version it may be) :-(...
I was looking at the changes for the next release and noticed the au
update command. Great, but why does it's progress messages go out
Hi all!
As I've announced earlier I'd like to start the machinery for the next
monotone release now that the database management branch has landed. So
if you have anything you'd also really like to see in the next monotone
version, please finish it up and merge it into mainline (I remember we
sti
Jack noted on irc that he couldn't look into the BSD issue yet and
Richard found no time to yet to take a look at the swedish translation
or the mtn conflicts functionality either - so despite we're all in a
hurry to get last minute presents for the relatives (at least the men
:)) I think there is
Richard Levitte schrieb:
Please, take a look at your translation and update if needed. The
current status is as follows on my machine (fresh pull and update):
fr.po: 753 translated messages, 180 fuzzy translations, 181 untranslated
messages.
ja.po: 592 translated messages, 243 fuzzy translatio
Hi,
I'm setting aside time on friday to release monotone 0.39.
Please, take a look at NEWS and update if needed.
Please, take a look at your translation and update if needed. The
current status is as follows on my machine (fresh pull and update):
fr.po: 753 translated messages, 180 fuzzy trans
On Wed, Feb 6, 2008 at 7:40 AM, Markus Schiltknecht <[EMAIL PROTECTED]> wrote:
> > Either way it goes, I wasn't considering waiting ENDLESSLY. I was
> > rather pondering if I should make a release this week (would be
> > friday) or next (would be that friday then).
>
> I'd personally vote for
Hi,
Richard Levitte wrote:
Either way it goes, I wasn't considering waiting ENDLESSLY. I was
rather pondering if I should make a release this week (would be
friday) or next (would be that friday then).
I'd personally vote for a release this week. If Zack considers nvm.e.e
mature enough to go
In message <[EMAIL PROTECTED]> on Wed, 6 Feb 2008 11:52:38 +, Nathaniel
Smith <[EMAIL PROTECTED]> said:
njs> My opinion is that every time we catch ourselves thinking
njs> "release" and "wait for ___" in close proximity, we should smack
njs> ourselves and go back to making the release. Remem
On Wed, 2008-02-06 at 11:41 +0100, Richard Levitte wrote:
> Hello,
>
> I'm thinking of making a release pretty soon, but I'm wondering if
> there's any opinion on what should be included. There are a few
> interesting development efforts going on, such as encapsulation and
> policy-branches, and
Hi,
Nathaniel Smith wrote:
My opinion is that every time we catch ourselves thinking "release"
and "wait for ___" in close proximity, we should smack ourselves and
go back to making the release. Remember the pathological spirals
*every* FOSS project used to get into back in the day, never
relea
On Wed, Feb 06, 2008 at 11:41:36AM +0100, Richard Levitte wrote:
> I'm thinking of making a release pretty soon, but I'm wondering if
> there's any opinion on what should be included. There are a few
> interesting development efforts going on, such as encapsulation and
> policy-branches, and the q
Hello,
I'm thinking of making a release pretty soon, but I'm wondering if
there's any opinion on what should be included. There are a few
interesting development efforts going on, such as encapsulation and
policy-branches, and the question is if we should wait for them to
become part of the main
Hi,
I said earlier that I intended to make a release today. Life being
what it is and me being exhausted as an effect, it didn't happen.
Sunday is the next possible day for me.
Cheers,
Richard
-
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html f
On Tuesday 27 February 2007, Nathaniel Smith wrote:
> (Same offer for anyone who makes the nightly coverage tracking stuff
> start working again; some changes in upstream matplotlib broke it a
> while back, and I haven't had time to get it running again since...
> the code is pretty straightforward
Hi,
Nathaniel Smith wrote:
Maybe I can offer a bribe or something? Free monotone shirt to anyone
who gets good mtn support into buildbot mainline? Or a cd or
something, I dunno? :-)
So that's buildbot code? I'll take a look at that, when time permits.
Where can I find the buildbot howte? Th
On Tue, Feb 27, 2007 at 01:39:22PM +0100, Markus Schiltknecht wrote:
> Hi,
>
> Richard Levitte - VMS Whacker wrote:
> >Unfortunately, it seems like the build bots are less than functional.
>
> Why is that? Can I help fixing that?
It looks like the problem is that the buildbot is currently using
Richard Levitte - VMS Whacker schrieb:
> In message <[EMAIL PROTECTED]> on Tue, 27 Feb 2007 14:26:32 +0100, Thomas
> Keller <[EMAIL PROTECTED]> said:
>
> me> Richard Levitte - VMS Whacker schrieb:
> me> > 349e77727a794a01eb0208c4b12b05c7bc31baac
> me>
> me> I did a fresh pull, but this rev is on
In message <[EMAIL PROTECTED]> on Tue, 27 Feb 2007 14:26:32 +0100, Thomas
Keller <[EMAIL PROTECTED]> said:
me> Richard Levitte - VMS Whacker schrieb:
me> > 349e77727a794a01eb0208c4b12b05c7bc31baac
me>
me> I did a fresh pull, but this rev is only a propagate from nvm to
me> nvm.cvssync.candidates
On Tuesday 27 February 2007, Richard Levitte - VMS Whacker wrote:
> me> nvm.cvssync.candidates was merged? When did that happen?
>
> 349e77727a794a01eb0208c4b12b05c7bc31baac
349e77727a794a01eb0208c4b12b05c7bc31baac is in nvm.cvssync.candidates only,
but d9df3690ffc222d7f6b1a65c34bfdfdcd6ad6735 is
Richard Levitte - VMS Whacker schrieb:
> In message <[EMAIL PROTECTED]> on Tue, 27 Feb 2007 13:47:35 +0100, Thomas
> Keller <[EMAIL PROTECTED]> said:
>
> me> nvm.cvssync.candidates was merged? When did that happen?
>
> 349e77727a794a01eb0208c4b12b05c7bc31baac
I did a fresh pull, but this rev is
In message <[EMAIL PROTECTED]> on Tue, 27 Feb 2007 13:47:35 +0100, Thomas
Keller <[EMAIL PROTECTED]> said:
me> nvm.cvssync.candidates was merged? When did that happen?
349e77727a794a01eb0208c4b12b05c7bc31baac
me> Also, if an incomplete revision is given (f.e. the revision
me> contains a patch f
In message <[EMAIL PROTECTED]> on Tue, 27 Feb 2007 13:39:22 +0100, Markus
Schiltknecht <[EMAIL PROTECTED]> said:
markus> Richard Levitte - VMS Whacker wrote:
markus> > Unfortunately, it seems like the build bots are less than functional.
markus>
markus> Why is that? Can I help fixing that?
If y
Richard Levitte - VMS Whacker schrieb:
> I think it's wise to make a release of
> e92a79a9a56076a4ead5013c29fb705a3c4de719, before the stuff from the
> nvm.cvssync.candidates was merged with the rest of nvm. The main
> reason is that some of the nvm.cvssync.candidates test break, and I
> can't tel
Hi,
Richard Levitte - VMS Whacker wrote:
Unfortunately, it seems like the build bots are less than functional.
Why is that? Can I help fixing that?
Regards
Markus
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/
Hi,
I think it's wise to make a release of
e92a79a9a56076a4ead5013c29fb705a3c4de719, before the stuff from the
nvm.cvssync.candidates was merged with the rest of nvm. The main
reason is that some of the nvm.cvssync.candidates test break, and I
can't tell if those failures are harmless or not.
No
In message <[EMAIL PROTECTED]> on Mon, 19 Feb 2007 11:17:13 -0800, Nathaniel
Smith <[EMAIL PROTECTED]> said:
njs> I was thinking of a release 'round about
njs> 19f1659a00d3df5076f768fba98463812a182a36
njs> which is where the 'ls unknown in subdir crashes' fix landed --
Yeah, I see what you mea
On Sat, Feb 17, 2007 at 11:02:28PM +0100, Richard Levitte - VMS Whacker wrote:
> There's been lots of talk about making a release. I was actually
> planning on doing one just before the summit, but got distracted, and
> when I saw all the good stuff that was being committed, I thought a
> release
Hi,
Richard Levitte - VMS Whacker wrote:
Personally, I would still
rather make a release of the latest there is, for the sake of making
things simple.
ACK. What were the reasons *not* to take the latest revision? Are those
issues fixable in a reasonable amount of time?
Markus
__
There's been lots of talk about making a release. I was actually
planning on doing one just before the summit, but got distracted, and
when I saw all the good stuff that was being committed, I thought a
release could wait.
Now, there's talk of making a release of what was there before the
summit.
On Fri, Mar 10, 2006 at 10:32:47AM +0100, Markus Meyer wrote:
> we are currently using Monotone 0.18 for version control in our
> business, which works great for us. However, from reading the webpage,
> it seems that there have already been some new versions released which
> require migration of th
"Justin Patrin" <[EMAIL PROTECTED]> wrote:
> *18*? Wow, that's a bit behind the times. A lot has changed.
It's not so hard to imagine. For example, Debian stable ships with
Monotone 0.18, and some people are happy working with packages only
found in the stable release of their favorite distribut
On 3/10/06, Markus Meyer <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> we are currently using Monotone 0.18 for version control in our
> business, which works great for us. However, from reading the webpage,
> it seems that there have already been some new versions released which
> require migratio
Hi everyone,
we are currently using Monotone 0.18 for version control in our
business, which works great for us. However, from reading the webpage,
it seems that there have already been some new versions released which
require migration of the database or even a complete rebuild of the
version his
89 matches
Mail list logo
