On 07/20/2010 05:44 AM, Stephen Leake wrote:
Timothy Brownawelltbrow...@prjek.net writes:
On 07/18/2010 08:19 AM, Stephen Leake wrote:
Tim,
Just letting you know I've been keeping up with nvm.options, and it all
looks very good so far.
I think it's ready to merge now. See anything I
On 07/21/2010 05:25 PM, Thomas Keller wrote:
Am 21.07.10 01:10, schrieb Thomas Keller:
Am 20.07.10 04:58, schrieb Timothy Brownawell:
On 07/18/2010 08:19 AM, Stephen Leake wrote:
Tim,
Just letting you know I've been keeping up with nvm.options, and it all
looks very good so far.
I think
On 07/26/2010 09:14 AM, Thomas Keller wrote:
I've talked with Thomas Moschny and he asked on ##c++ for a proper
solution of the problem. The answers were mainly to replace all custom
type specializations with real types, i.e. basically what I did
above, so u32, u64, size_t and all the others
.
--
Revision: 78f4db157a353de19b33df875959efc2492812b4
Parent: c36b63fe53580cdf51cd5c6afa42fc4a30a1d095
Author: Timothy Brownawell tbrow...@prjek.net
Date: 07/27/2010 09:28:25 PM
Branch: net.venge.monotone
Changelog
On 07/23/2010 03:42 AM, Stephen Leake wrote:
should we hide --min/max-netsync-version?
Sounds like a good idea, I've added that.
--
Timothy
Free public monotone hosting: http://mtn-host.prjek.net
___
Monotone-devel mailing list
On 07/21/2010 06:15 PM, Thomas Keller wrote:
Am 21.07.10 01:10, schrieb Thomas Keller:
If the compilation issue is fixed, I'll check the UI again and may come
up with other little things :)
Some more observations:
- --verbosity changes the level between -2 and 1 (default is 0) - but I
On 07/20/2010 06:10 PM, Thomas Keller wrote:
I wished that you'd have commented a few places a bit more though for us
other devs so we properly use the new / changed macros
(CMD_PRESET_OPTIONS is not mentioned f.e.) and have an idea what certain
code paths do (just out of my head here, the
On 07/21/2010 05:18 AM, Stephen Leake wrote:
The options no-unknown/unknown are defined twice - once as
SIMPLE_OPTION(unknown ...)
once as
OPTSET_REL(automate_inventory_opts, no_unknown)
SIMPLE_OPTION(no_unknown ...)
That seems like it could be a problem, but it seems to work.
Yeah...
On 08/09/2010 06:28 PM, Thomas Keller wrote:
- If I increase the verbosity to 2 or set --verbosity=2, the --debug
output is shown (which is reasonable, but not yet documented in the
option text)
Whats up with that? Now that --verbosity=1 has no effect on the above
mentioned commands
On 08/10/2010 07:03 AM, Thomas Keller wrote:
Am 10.08.2010 13:51, schrieb Timothy Brownawell:
On 08/09/2010 06:28 PM, Thomas Keller wrote:
- If I increase the verbosity to 2 or set --verbosity=2, the --debug
output is shown (which is reasonable, but not yet documented in the
option
On 08/10/2010 12:31 PM, Derek Scherger wrote:
Sorry, I've been away and I'm late to the party on this but I'm not sure
I like the --verbosity, --quiet, --debug and --reallyquiet options all
that much.
What about this as an alternative:
- default verbosity is 0 as described above
- verbosity
On 08/14/2010 07:06 PM, Stephen Leake wrote:
Timothy Brownawelltbrow...@prjek.net writes:
On 08/10/2010 12:31 PM, Derek Scherger wrote:
Sorry, I've been away and I'm late to the party on this but I'm not sure
I like the --verbosity, --quiet, --debug and --reallyquiet options all
that much.
Short version: I'd like to use ';' as a URI argument separator, and
error out if both a query parameter and a separate include pattern are
given. Are there any objections to this?
$ mtn sy
mtn://mtn-host.prjek.net/webohst?'net.venge.monotone.{viewmtn,contrib.{webhost,usher}}*'
mtn: misuse:
On 08/30/2010 03:09 AM, Richard Levitte wrote:
Another way to handle it is to expand the pattern early into an array
of strings using globish and teaching monotone to handle that.
That would work better if we didn't have the first-position argument
mean something different than later
On 08/30/2010 08:34 AM, Richard Levitte wrote:
Hmmm, it seems we're reaching an unhealthy level of complexity
regarding this... Maybe it's time to invoke the KISS principle and
rethink?
Erroring out when given both query parameters and separate include
arguments seems like it should be
On 09/20/2010 07:23 PM, Brian May wrote:
Hello,
I asked a similar question on my local mailing list concerning git.
Just wondered what perspective I would get here, in particular with
monotone people. I think similar issues apply in both cases.
Lets say I am tracking an upstream project. As I
On 09/26/2010 09:36 AM, Stephen Leake wrote:
In implementing the DVC front-end for automate sync, I've run into a
problem.
If I use ssh: or file: netsync schemes, the mtn process that is started
outputs startup error messages that are not properly packetized for
automate stdio. For example, if
On 10/04/2010 07:32 AM, Thomas Keller wrote:
Please review the above branch. The branch name has not so much in
common with the actual implementation anymore, though:
* a new file_sizes table has been added which records the size
in bytes of individual files
* two new automate commands have
On 10/07/2010 04:45 AM, Thomas Keller wrote:
Hi all!
I already brought up the idea on IRC some time ago - I am looking for a
way to restrict allowed incoming revisions on the server-side. No, I
don't plan to go towards the complexity of policy branches, which Tim is
working on for quite some
On 10/10/2010 08:20 AM, Lapo Luchini wrote:
I've seen this in 0.40, but I still have issues in 0.48 (on FreeBSD):
% LANG=C mtn version
monotone 0.48 (base revision: 844268c137aaa783aa800a9c16ae61edda80ecea)
% LANG=C mtn pull 'mtn://code.monotone.ca/monotone?*'
mtn: setting default include
With the new splitted server databases, the 'monotone' and 'contrib' servers
need some rather involved sync patterns if you're going to be syncing everything
to the same local database. The below patterns should work if you start with a
fresh database, otherwise there are several additional things
There is an actual release of usher available now. It's tagged as
usher-0.99 available from
mtn://monotone.ca/contrib?net.venge.monotone.usher
and there is a tarball available at
http://mtn-host.prjek.net/projects/webhost/files/usher-0.99.tar.gz
. It works on at least Debian and FreeBSD.
On 11/08/2010 01:49 PM, Hendrik Boom wrote:
On Fri, Nov 05, 2010 at 11:46:03PM -0500, Timothy Brownawell wrote:
There is an actual release of usher available now. It's tagged as
usher-0.99 available from
mtn://monotone.ca/contrib?net.venge.monotone.usher
and there is a tarball available
On 11/08/2010 01:04 PM, Hendrik Boom wrote:
On Fri, Nov 05, 2010 at 11:46:03PM -0500, Timothy Brownawell wrote:
There is an actual release of usher available now. It's tagged as
usher-0.99 available from
mtn://monotone.ca/contrib?net.venge.monotone.usher
and there is a tarball available
On 11/08/2010 12:36 PM, Hendrik Boom wrote:
Well, I did download the tarball,
http://mtn-host.prjek.net/projects/webhost/files/usher-0.99.tar.gz
and untarred it. The README file says
The documentation is in doc/documentation.html.
But there is no doc directory to be found in the
On 11/09/2010 10:31 PM, Hendrik Boom wrote:
On Tue, Nov 09, 2010 at 08:50:26PM -0600, Timothy Brownawell wrote:
On 11/08/2010 01:49 PM, Hendrik Boom wrote:
On Fri, Nov 05, 2010 at 11:46:03PM -0500, Timothy Brownawell wrote:
There is an actual release of usher available now. It's tagged
On 11/22/2010 07:23 AM, Thomas Keller wrote:
We already append a suffix dev to development snapshots (i.e.
1.0dev) which get created on build farms like openSUSE's build
service. Thomas Moschny said that this is suboptimal because of rpm's
version comparison algorithms which would consider
On 11/22/2010 09:43 AM, Hendrik Boom wrote:
This if we add ~dev7 to version number 1.1, we'll get version 1.1~dev7,
which will sort before version 1.1
This sounds like the numbering system we're looking for.
Of course, this isn't the *entire* comparison alrorithm. There's also
an epoch and a
On 11/22/2010 10:48 PM, Hendrik Boom wrote:
On Mon, Nov 22, 2010 at 11:46:49PM -0500, Hendrik Boom wrote:
On Mon, Nov 22, 2010 at 05:28:23PM -0600, Timothy Brownawell wrote:
On 11/22/2010 09:43 AM, Hendrik Boom wrote:
This if we add ~dev7 to version number 1.1, we'll get version 1.1~dev7
:
tbrownawOn Mon, Nov 22, 2010 at 05:28:23PM -0600, Timothy Brownawell
wrote:
tbrownawOn 11/22/2010 09:43 AM, Hendrik Boom wrote:
tbrownawThis if we add ~dev7 to version number 1.1, we'll get version
tbrownaw1.1~dev7,
tbrownawwhich will sort before version 1.1
tbrownaw
tbrownaw
On 11/19/2010 04:31 AM, Markus Wanner wrote:
Hi,
I've recently upgraded to monotone 0.99, mainly to get the new commit
message editor. Thanks for that!
However, it seems to me it's quite a bit slower than previous versions.
Which weren't exactly fast, either, but 'mtn status' and 'mtn ls
On 11/27/2010 10:55 PM, Timothy Brownawell wrote:
On 11/19/2010 04:31 AM, Markus Wanner wrote:
Hi,
I've recently upgraded to monotone 0.99, mainly to get the new commit
message editor. Thanks for that!
However, it seems to me it's quite a bit slower than previous versions.
Which weren't
On 11/29/2010 05:10 AM, Markus Wanner wrote:
On 11/28/2010 07:55 PM, Timothy Brownawell wrote:
Do we mind having an index-only schema change between 0.99 and 1.0? It
sounds like we'd get a noticeably better user experience...
I'd certainly appreciate it, but maybe someone who values the 1.0
On 11/29/2010 01:05 PM, Markus Wanner wrote:
Each revision typically has 4 certs (author, branch, date, changelog), so the
old index on only rev_id should usually give 5 lookups. Indexing on (rev_id,
name, value) should usually give 2 lookups, and indexing on everything gives
1 lookup.
..at
On 12/04/2010 06:27 AM, CooSoft Support wrote:
Firstly if I want to update the wiki exactly what db do I use and
branch, I can't find anything to do with wikis in any database that I
can browse... Also if I don't have write access to it can I be granted
write access please.
It's a proper
The net.venge.monotone.visualc branch builds and passes the tests on
MinGW and *nix. With Visual Studio it passes the tests except for 3 i18n
failures. Do we want to merge this now (and have 1.0 be buildable on
VS2010) or wait for after the release?
The changes are largely:
* I built
On 01/08/2011 05:02 PM, Thomas Keller wrote:
Am 08.01.11 17:29, schrieb Stephen Leake:
I'm adding a description of the global options to monotone.texi.
What is the use case for :memory: database?
One is for example that it gives you a throw-away database for remote
automate actions: If you
On 01/08/2011 06:19 PM, Stephen Leake wrote:
Correct. But it would be nice to document how the executables on our
download page are built. In fact, that's a requirement of the GPL 3
license
Some of our downloads like the Windows installer bundle the libraries we
use. So for any copyleft
On 01/09/2011 04:16 AM, Stephen Leake wrote:
Timothy Brownawell tbrow...@prjek.net writes:
(which we should upgrade to).
Eww.
Can you elaborate? GPL 3 is technically more sophisticated than GPL 2.
Mostly I'm annoyed at the change from straight copyleft to forbidding it
from being used
On 01/30/2011 05:08 PM, Thomas Keller wrote:
Hi all!
Richard, Stephe and me polished the above branch over the last weeks and
got positive response from a couple of people that it works well for
them. For those who weren't following the previous development, this
branch is basically about
On 01/31/2011 07:36 PM, Stephen Leake wrote:
this gets back to the question I asked:
What Makefile targets are supposed to work?
I tested monotone.pdf, but not monotone.ps. Is there some other target
that builds monotone.ps? 'dist' apparently doesn't.
What other targets do I need to
On 04/13/2015 03:02 AM, Markus Wanner wrote:
That's a use case. Have --pager be a GUI program (notepad, whatever),
which doesn't output thru your terminal. In which case you probably want
it *especially* if your terminal isn't smart.
Such a program would need to be able to read from stdin, but
On 04/09/2015 01:23 PM, Markus Wanner wrote:
Hi,
On 03/30/2015 08:48 PM, Markus Wanner wrote:
To argue a bit more objectively: I tried to make the default colors
readable on black as well as white background. And I reduced noise a bit
by un-coloring a couple of things. Colorization can be
On 04/12/2015 01:59 PM, Markus Wanner wrote:
Other colorized commands will output the colorization codes if
specifically asked, even to pipes.
That in turn surprises me.
$ mtn diff --colorize | cat
gives monochrome output for me. What specific command and OS do you use?
Oops, I meant
mtn-host.prjek.net has been unmaintained for far too long, and is almost
unused (no more than 5 projects touched this year). I'll be making it
read-only in mid-November, and then taking it the rest of the way down
at the end of the year.
___
On 11/27/2015 07:03 AM, Hendrik Boom wrote:
I'm specfically looking to find out how to get usher to reread the
configuration file.
It tries to be a good Unix daemon, and catches SIGHUP for this. There's
also a command thru usherctl.
Either it didn't work, or I don't know how to SUGHUP.
I
On 11/21/2015 07:47 PM, Hendrik Boom wrote:
Where does usher documentation hide out now?
It's in doc/documentation.html . I don't know that this is available
online anywhere other than thru viewmtn.
I'm specfically looking to fine out how to get usher to reread the
configuration file.
It
On Thu, 2016-01-21 at 19:25 -0500, Hendrik Boom wrote:
> In all the examples I've seen, in the read permissions file I get to
> use a pattern to specify which branches users are allowed to read.
>
> But there seems to be no such pattern in the write permissions file.
>
> Is there a reason for
501 - 548 of 548 matches
Mail list logo
