On Thu, 2006-04-27 at 08:13 +0200, [EMAIL PROTECTED] wrote:
it seems to me that on windows, the size of the output in the response of
'mtn automate stdio' is evaluated
_before_ line endings are expanded to CRLF:
The real error is that automate stdio output is binary, and should not
be
Hello,
I found a bug in 0.24, it still exist in 0.26. This is on windows.
Scenario:
You have a working directory with some version controlled files. Change the
permission of them to read only. Sync the monotone database with someone
that has made changes. Do mtn update, monotone will now crash
Hello,
This is more of an question than a bug report:-)
Currently it's not possible to do:
$ mtn commit -m
mtn: beginning commit on branch 'test'
mtn: misuse: log message rejected: empty messages aren't allowed
But it's possible to do:
$ mtn commit -m
mtn: beginning commit on branch 'test'
Well, I found them interesting to read, anyway :-):
http://www.selenic.com/mercurial/wiki/index.cgi/UserSurvey
-- Nathaniel
--
But in Middle-earth, the distinct accusative case disappeared from
the speech of the Noldor (such things happen when you are busy
fighting Orcs, Balrogs, and
Nathaniel Smith schrieb:
Well, I found them interesting to read, anyway :-):
http://www.selenic.com/mercurial/wiki/index.cgi/UserSurvey
Two quotes interesting to us would be (comments about other known SCM):
Chose Monotone, got confused, switched to Mercurial.
I don't know anything about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Keller wrote:
Nathaniel Smith schrieb:
snip
Monotone is simply too slow to use, even on smallish trees on my dual
amd64.
The obvious bottle-neck IMHO is pulling large repos, like the monotone
one,
Pulling the monotone repo could have
Hi.
I have written a small section for the annotate command.
I don't know if this kind of humore is OK for the manual,
but well, there it is.
J.
patch.annotate.texi
Description: TeXInfo document
___
Monotone-devel mailing list
Thomas Keller wrote:
Chose Monotone, got confused, switched to Mercurial.
While I have some issues with the monotone model as well (ie. branch as
a bag of (possibly) unrelated discontinuous revisions) I do not find it
any more 'difficult' than mercurial's.
Monotone is simply too slow to use,
On Thu, 2006-04-27 at 09:43 +0200, Johan Bolmsjö wrote:
Hello,
This is more of an question than a bug report:-)
Currently it's not possible to do:
$ mtn commit -m
mtn: beginning commit on branch 'test'
mtn: misuse: log message rejected: empty messages aren't allowed
But it's
Matthias Hoelzl [EMAIL PROTECTED] writes:
[...]
Is there some way for me to get rid of these certificates or (even
better) to sign them with my key or have him sign them with his good
key?
Creating new certs is easy, just use monotone cert rev name
value. So you can easily produce well
Timothy Brownawell wrote:
It's the default version of the validate_commit_message hook. I don't
think it's a very good default, so would anyone object to removing it?
bikeshed
I definitely think that rejecting empty log messages by default is a
good thing. I'd also go with rejecting
On Thu, 2006-04-27 at 09:38 +0200, Johan Bolmsjö wrote:
Hello,
I found a bug in 0.24, it still exist in 0.26. This is on windows.
...
[EMAIL PROTECTED] ~/test/foo
$ chmod 444 bar
[EMAIL PROTECTED] ~/test/foo
$ ls -l
total 1
drwxr-xr-x2 johanAdminist0 Apr 27 07:21 _MTN
On 4/27/06, Jon Bright [EMAIL PROTECTED] wrote:
Timothy Brownawell wrote:
It's the default version of the validate_commit_message hook. I don't
think it's a very good default, so would anyone object to removing it?
bikeshed
I definitely think that rejecting empty log messages by default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Patrin wrote:
On 4/27/06, Jon Bright [EMAIL PROTECTED] wrote:
Timothy Brownawell wrote:
It's the default version of the validate_commit_message hook. I don't
think it's a very good default, so would anyone object to removing it?
bikeshed
I
On Thu, Apr 27, 2006 at 07:03:00AM -0300, Jeronimo Pellegrini wrote:
I think a $ was missing in the packet tutorial...
Indeed.
Also, maybe this introductory paragraph would be nice?
Yes, it would. I'll tweak your wording ever so slightly, but will add
this change shortly.
Thanks!
--
Dan.
On Thu, Apr 27, 2006 at 01:57:21PM -0500, Timothy Brownawell wrote:
But when doing it
form the command line I can only assume that you folks don't like empty
commit messages. If that is the case I think that the second example should
fail too (only white space in commit message).
On 4/27/06, Nathaniel Smith [EMAIL PROTECTED] wrote:
On Thu, Apr 27, 2006 at 01:57:21PM -0500, Timothy Brownawell wrote:
But when doing it
form the command line I can only assume that you folks don't like empty
commit messages. If that is the case I think that the second example
On Thu, Apr 27, 2006 at 11:28:27AM +0200, Koen Kooi wrote:
Pulling the monotone repo could have been nearly twice as fast, since
almost half of the revisions are merges. 'commit before update' is
great, but PR wise you are shooting yourselves in the foot IMO.
Well, maybe. We _should_ be fast
On Thu, Apr 27, 2006 at 02:45:53PM +0200, Georg-W. Koltermann wrote:
Hg really appeals to me. Picking Hg or monotone mainly becomes a matter
of your preference for either a more star-like topology with a couple of
oligarchic interconnected repositories keeping all the history (well, to
the
On Friday 28 April 2006 00:03, Nathaniel Smith wrote:
On Thu, Apr 27, 2006 at 11:28:27AM +0200, Koen Kooi wrote:
Pulling the monotone repo could have been nearly twice as fast, since
almost half of the revisions are merges. 'commit before update' is
great, but PR wise you are shooting
On Thu, Apr 27, 2006 at 03:36:20PM -0700, Justin Patrin wrote:
For those of you who don't know we've solved this problem for
OpenEmbedded by having a snapshot database for download on a system
which is updated every night. This was when people are just starting
they can grab the snapshot and
On Thu, Apr 27, 2006 at 04:26:12PM -0700, Nathaniel Smith wrote:
As it happens, the actual checking proper seems to be almost invisible
in profiles of 0.26's pulls. There's still some reason to think that
this is all doable. So, that's why I think we should keep trying the
improve speed
Greetings,
During my dealings with my monotone server today, I had to restart it to
change the branch patterns it serves. This got my wheels turning, and
after some discussion on IRC, I discovered that the branch arguments to
mtn serve, duplicate the functionality of the
23 matches
Mail list logo
