On Thu, Mar 09, 2006 at 09:44:50AM +0300, Petr Ovtchenkov wrote:
May be I miss something, but can you clarify the status of 0.26 and
procedure of pull from venge.net?
[the reason of question is a problems with pull with 0.26pre1 client,
inspired by two heads in net.venge.monotone branch].
I
On Thursday 09 March 2006 15:08, Nathaniel Smith wrote:
On Thu, Mar 09, 2006 at 09:44:50AM +0300, Petr Ovtchenkov wrote:
May be I miss something, but can you clarify the status of 0.26 and
procedure of pull from venge.net?
[the reason of question is a problems with pull with 0.26pre1
I am willing to pay a good bounty for a reproducible build process for
monotone-viz on cygwin. That is, whatever needs to be done to
monotone-viz or to the environment that will get it to compile against
a basic cygwin installation, the monotone-viz included lablgtk, and a
monotone compiled
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
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 migration of
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
On 2/7/06, Olivier Andrieu [EMAIL PROTECTED] wrote:
Hi,
I've just released monotone-viz 0.13
...
Call me crazy, but I can't find the branch drop-down box in monotone-viz 0.13.
Cheers,
Shaun
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
Chad Walstrom wrote:
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
Nathaniel Smith wrote:
Why switch?
-- Real-world usage shows, many many users do not like the long
name, and alias it to something shorter.
Yay for MTN!!!
I'm a mtn user since day 0, AFAIR I created the symlink even before
trying it ;-)
(and before discovering other people were using
On Sun, 2006-02-26 at 20:43 -0600, Timothy Brownawell wrote:
-- mtn -- the boring, generic choice. Of course, sometimes boring
is good.
It's also what I use, so it's clearly superior. :p
I agree, although not for this reason.
I never found typing monotone to be too much of an
Could someone with access to both unix and win32 monotone's try:
-- on unix, checking in a tree containing a file named mt/foo
-- on windows, checking out this tree, and reporting on what
happens? Especially, whether the file mt/foo ends up in MT/?
It would be nice to know for both 0.25
[EMAIL PROTECTED] wrote:
Should we want to differentiate ourselves in google searches, perhaps
trying a few names on google now might be useful.
mmm -- 8,490,000 Google hits
mm -- 109,000,000
m -- 1,340,000,000
mtn -- 6,410,000
mon -- 206,000,000
monotone -- 2,950,000
But as Google
On Wed, Mar 01, 2006 at 12:18:58PM +1100, Daniel Carosone wrote:
If this is to change, let's please use .MTN (or equivalent for the
eventual name), and make it selectable by a hook in
~/monotone/monotonerc or the environment.
I'm not going to make any pronouncements about what might be
On Saturday 04 March 2006 10:15, Nathaniel Smith wrote:
Could someone with access to both unix and win32 monotone's try:
-- on unix, checking in a tree containing a file named mt/foo
-- on windows, checking out this tree, and reporting on what
happens? Especially, whether the file
On Saturday 04 March 2006 09:46, Nathaniel Smith wrote:
So the possibilities that come to my mind are:
-- Use .mtn for the bookkeeping dir, and keep .monotone as the
config dir. This seems sort of weird, though I guess it's what
both bzr-ng and svn do. I also share Matt's mild
On Sat, Mar 04, 2006 at 12:46:52AM -0800, Nathaniel Smith wrote:
The other exciting thing is that in my first email, I forgot about the
config directory, ~/.monotone. Presumably this name should also match
the name of the executable.
Oh, I dunno. All the .stuff should be .monotone* surely?
Nathaniel Smith njs at pobox.com writes:
To spoil the ending, I'm going to suggest we switch to the name mtn
for 0.26 and going forward.
I'm definitely for it... partly because I like innovation/change, but even more
so because it would be no change at all for me: as far as I remember I did
Another vote for 'mtn' from me.
Gut reaction to other contenders (in addition to all being poorer
abbreviations):
mt: name collisions are bad
m: too cute
mmm: too annoying to type
moto: just don't like it ;)
But none of the possible outcomes will make me howl with rage or
anything.
-emile
In message [EMAIL PROTECTED] on Sun, 05 Mar 2006 07:07:10 +0100 (CET),
Richard Levitte - VMS Whacker [EMAIL PROTECTED] said:
richard Anyway, I think my piece on the subject...
That was supposed to be Anyway, I think I've said my piece...
Cheers,
Richard
-
Please consider sponsoring my
19 matches
Mail list logo
