Hi all,
It's been a long time since I've hacked on monotone. At work we use CVS for
our development, and for a variety of reasons that's not likely to change.
The group I work with would like to set up a sort of experimental
development repository to allow us to hack on stuff that is potentially
There's a link off of the monotone home page. It's channel #monotone on
irc.oftc.net I think.
-emile
On Sat, Jan 17, 2009 at 8:16 AM, Stephen Leake
stephen_le...@stephe-leake.org wrote:
Where is the IRC? I can't find instructions for that on the mtn wiki
(I _really_ miss the search facility
I am fine with anything I contributed to the manual being released under
the GPL, v2 or later (although I don't think I have anything
sufficiently substantive to matter).
-Emile Snyder
(And hi to all you monotone developers; long time no see. Hope all is
well with everyone.)
On Sun, 2007-02-18
Hi Vesselin,
I worked on the annotate stuff alot back in the day, but haven't had
much time to devote to monotone lately. So I'll do my best to figure
this out, but I might not be able to give it the time it needs...
You mention wrong character case of the filename in the subject; can you
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
On Fri, 2006-03-03 at 22:37 +0100, Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Emile Snyder wrote:
On Fri, 2006-03-03 at 20:56 +0100, Tim Ansell wrote:
snip
Say in CVS, when I create a branch called Mithro's Changes I now have
two heads, the latest version
On Wed, 2006-02-08 at 13:46 +0300, Zakirov, Salikh wrote:
... git allows a more fully distributed
model making it easier for users to pull (even speculatively with
fetch) from multiple sources, track them in the local repository
as separate branches and merge when appropriate.
This is
Someone on IRC had an issue today where they did
monotone sync servername 'branchname'
and it pulled 0 revisions. They then tried
monotone sync servername branchname
and were successful. The were running monotone on windows; I seem to
recall someone else getting confused like this before
Hi all,
I've been experimenting on net.venge.monotone.annotate with making
annotate faster by keeping a DAG in the database of the revisions
modifying each file. This could conceivably be used to speed up certain
log operations as well (although at the moment it's just revisions which
have
On Thu, 2005-10-27 at 19:57 +0200, Jon Bright wrote:
Emile Snyder wrote:
No, this is clearly a bug in monotone. You created a legal file on your
system in the working copy, and monotone choked and died. Thanks for
digging and figuring it out,
An interesting question - should
I vote for in tree, and part of standard releases. Serving multiple
distinct projects a'la CVS from the same server comes up repeatedly on
the mailing list as something people would like to do. If monotone's
answer is to have a separate utility to do it (and I like what I've seen
of usher so far
Yuck. cert.cc:guess_branch(revision) defaults to using
app.branch_name() if one is set; ie. you are in a working copy.
There are 4 commands using guess_branch to decide how to cert a new
revision:
approve
disapprove
checkout
commit
I would argue that only commit should default to using the
On Tue, 2005-10-25 at 18:50 +0100, Bruce Stephens wrote:
Emile Snyder [EMAIL PROTECTED] writes:
I would argue that only commit should default to using the working copy
value if one is set. approve and disapprove both take a revision as a
specific argument; I can sort of see using the value
Hi all,
I'd like to put together an 'early adopters' page for the monotone
website that gives links to publicly accessible projects using monotone,
along with some quick stats (size of db, number of committers, number of
revs, etc.).
Evaluating a tool is hard if you don't have any full-scale
On Thu, 2005-10-20 at 13:46 -0700, Justin Patrin wrote:
OpenEmbedded is using monotone currently.
http://openembedded.org
Looks like we currently have 39 public keys in our DB, although the #
of regular comitters is 10 or less I think. We have 3+ servers set up
to sync with each other and
Hi all,
Do people think that an h:branch selector to find the heads of a branch
should accept globbing wildcard characters like the b: selector? So if
you said
a:bozo/h:com.circus.*
it would select any head of a branch in the com.circus.* set authored by
bozo. There has been concern
I believe I had exactly this problem on a newer redhat system at work.
I don't pretend to understand exactly what's going on, but for me it
appeared that /lib/tls/libc.so.6 didn't like exceptions at all (a
trivial small test program that tried throwing and catching an exception
died in the same
On Thu, 2005-10-13 at 00:15 -0700, Emile Snyder wrote:
Hi all,
Do people think that an h:branch selector to find the heads of a branch
should accept globbing wildcard characters like the b: selector? So if
you said
Ok, no one argued against it, there were a couple of lukewarm might
On Thu, 2005-10-13 at 10:22 +0200, Wim Oudshoorn wrote:
From a quick look in the manual I get the impression that:
* All selectors accept globbing except:
- date related selectors
- ID selector
This seems reasonable to me, dates and IDs have a very restricted
format. So for
On Thu, 2005-10-13 at 12:58 -0700, Nathaniel Smith wrote:
Oh, yes, please -- I definitely think h:nothing should mean
h:current branch...
Ok, will do.
(For that matter, perhaps b:nothing should mean b:current branch.)
Can do that too.
-emile
Hi all,
Below is a patch, per the venge.net/monotone/quickies.html list, to
change the monotone serve syntax from
monotone serve ADDRESS[:PORT] PATTERN ...
to
monotone [--bind=[ADDRESS:]PORT] serve PATTERN ...
where, if you leave out ADDRESS it listens on all interfaces, which is
also the
to be the address to listen on as another pattern for branches to
export.)
thanks,
-emile
On Tue, 2005-10-11 at 15:19 -0700, Emile Snyder wrote:
Hi all,
Below is a patch, per the venge.net/monotone/quickies.html list, to
change the monotone serve syntax from
monotone serve ADDRESS[:PORT] PATTERN
Is your shell expanding *? I would think the command should be
monotone serve 0.0.0.0 '*'
-emile
On Wed, 2005-10-12 at 01:17 +0200, Wim Oudshoorn wrote:
When I server all branches with
monotone serve 0.0.0.0 *
I can not sync from other computers, I get an error
something like:
Is this in a project that you could let me see, or proprietary code? It
would make it much easier to debug if I could do a pull of your project
db.
thanks,
-emile
On Sun, 2005-10-09 at 14:55 +0200, Wim Oudshoorn wrote:
In one project containing 3 files the command
monotone annotate file
I like the idea of an .mt-attrs approach because the binary'ness of a
file is a property of the file, not something that different people
should have different ideas about (a'la hooks).
I don't have particularly strong feelings about the right way to help
monotone automatically figure it out for
On Sat, 2005-05-14 at 21:21, Derek Scherger wrote:
it seems to me that there are three settings for such a hook
- fail on pre-existing files
(cvs, svn, etc. do this)
- preserve pre-existing files but continue
(which I think would be useful occasionally)
- clobber pre-existing files
See tests/t_add_stomp_file.at ;)
-emile
On Tue, 2005-05-10 at 10:52, Robert Bihlmeyer wrote:
Suppose I have two working copies A and B, and an unknown file F in
both. I then add A/F, commit this, and finally update B. monotone will
trample over the contents of B/F overwriting it with the
On Mon, 2005-05-02 at 10:48, Timothy Brownawell wrote:
On 5/2/05, Henrik Holmboe [EMAIL PROTECTED] wrote:
Nathaniel Smith [EMAIL PROTECTED] writes:
snip
command-specific-option. For this to be acceptable, though, I think on
drop we'd have to cache the deleted file somewhere, for disaster
On Thu, 2005-04-21 at 00:55, Richard Levitte - VMS Whacker wrote:
...snip...
I'm proposing to change that behavior by making things more explicit.
Instead of getting implicitely stuck on revisions with true testresult
certs, there should be a way to explicitely ask to get only those. As
fat
Hi all,
Is it worth looking at cvs bugs on the main branch, or is the cvssync
branch going to supersede it? Is cvssync close to merging? Is cvssync
stable enough that I should try to figure out bugs on it, or is it still
in flux and I should just let Christof do his thing?
thanks,
-emile
On Mon, 2005-04-18 at 05:36, Christof Petig wrote:
...
I imported the test. But currently I have a problem of zombie revisions
appearing on cvs_pull (currently dead files reappear).
I'll tackle the problem later this week (sorry)
No sweat, just wanted to make sure it got through to you.
31 matches
Mail list logo
