Nathaniel Smith <[EMAIL PROTECTED]> wrote:
For the convenience of people who want to keep an eye on release
announcements and such, but don't want to hear about all the ongoing
chatter, a new, low-volume, moderated list is now available:
List address: [EMAIL PROTECTED]
Request address: [EMAIL
In message <[EMAIL PROTECTED]> on Thu, 12 Jan 2006 11:57:36 +0100, Olivier
Andrieu <[EMAIL PROTECTED]> said:
oliv__a> My latest commit is andrieu/2006-01-08T15:04 .
d677d8bffbb6afb97e06de3f0fc0f6059969ed2b
oliv__a> If it's a parse error you should get an error window when
oliv__a> clicking on a
Hej Richard,
Richard Levitte - VMS Whacker [Thursday 12 January 2006] :
> I've built monotone-viz (latest possible incarnation) with 0.26pre1
> (well, actually, latest possible incarnation of mainline monotone as
> well),
My latest commit is andrieu/2006-01-08T15:04 .
> and am noticing tha
Suppose someone (with suitable access) decided to start rearranging
monotone.texi, and committed a revision on n.v.m that removed
monotone.texi (the idea being that Makefile would create it from
smaller files, I guess).
Anyway, it's resolved that that's not a good idea, so how do you
recover?
On Thu, Jan 12, 2006 at 08:44:44AM +, Daniel THOMPSON wrote:
> Nathaniel Smith <[EMAIL PROTECTED]> wrote:
> >For the convenience of people who want to keep an eye on release
> >announcements and such, but don't want to hear about all the ongoing
> >chatter, a new, low-volume, moderated list is
Justin Patrin <[EMAIL PROTECTED]> writes:
[...]
> Forgive me if I'm being ignorant somehow (I'm not a heavy monotone
> user) but isn't this what "disapprove" is for?
No. disapprove commits a reversal of a revision. So if I have a
graph:
digraph G {
base -> a;
a -> b;
b
Last month Daniel Carosone proposed to store the corresponding CVS
revisions for a given (imported or cvssynced) monotone revision within
the usual files: */CVS/Entries, */CVS/Repository instead of using a
hidden file (like .mt-cvs_revisions).
I see some drawbacks and some benefits, what do you th
On Thu, Jan 12, 2006 at 11:57:36AM +0100, Olivier Andrieu wrote:
> Sure, shouldn't take much time ... if you can provide me with a
> revision that trips m-viz or, better, if you can point me to the
> precise grammar of revisions.
Probably a good thing to look at, since there are definitely things
In message <[EMAIL PROTECTED]> on Thu, 12 Jan 2006 09:56:28 -0800, Nathaniel
Smith <[EMAIL PROTECTED]> said:
njs> Probably the "automate get_revision" documentation in the manual
njs> is wrong and misleading now.
Speaking of formats, I find it a bit surprising that the revision for
a merge only
On 1/12/06, Bruce Stephens <[EMAIL PROTECTED]> wrote:
> Suppose someone (with suitable access) decided to start rearranging
> monotone.texi, and committed a revision on n.v.m that removed
> monotone.texi (the idea being that Makefile would create it from
> smaller files, I guess).
>
> Anyway, it's
Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]> on Thu, 12 Jan 2006 09:56:28 -0800, Nathaniel
> Smith <[EMAIL PROTECTED]> said:
>
> njs> Probably the "automate get_revision" documentation in the manual
> njs> is wrong and misleading now.
>
> Speaking of
Richard Levitte - VMS Whacker [Thursday 12 January 2006] :
> oliv__a> If it's a parse error you should get an error window when
> oliv__a> clicking on a node
>
> Yup, "Error while parsing revision set of {ID}", with {ID} being the
> revisions ID.
>
> oliv__a> Could you extract some of the
Bruce Stephens <[EMAIL PROTECTED]> writes:
[...]
> I think that would be a bug, but I don't think it's true, is it? For
> example, ff8534867e5887ee95b64b7d3e931fc6fdf5dbd2 is a merge of
> 06c7bee4908ccedcc08af304925b75aefcd93e3e and
> 41eef7bebdea151436fc9f0331f6297e64e8a491, and has two old_rev
On Thu, Jan 12, 2006 at 01:58:16PM +, Bruce Stephens wrote:
> I guess you could merge, but edit out the changes from this fork, but
> that's annoying and (if I understand the lifetime issues correctly)
> can't remove the deletion of monotone.texi as one would hope (once a
> file is dead in any
On Thu, Jan 12, 2006 at 10:04:24PM +0100, Richard Levitte - VMS Whacker wrote:
> In message <[EMAIL PROTECTED]> on Thu, 12 Jan 2006 09:56:28 -0800, Nathaniel
> Smith <[EMAIL PROTECTED]> said:
>
> njs> Probably the "automate get_revision" documentation in the manual
> njs> is wrong and misleading
On Thu, Jan 12, 2006 at 11:00:54PM +, Bruce Stephens wrote:
> I guess db rosterify doesn't rewrite the ids in changelogs?
Ah, correct, it does not.
-- Nathaniel
--
Damn the Solar System. Bad light; planets too distant; pestered with
comets; feeble contrivance; could make a better one mysel
In message <[EMAIL PROTECTED]> on Thu, 12 Jan 2006 22:39:46 +, Bruce
Stephens <[EMAIL PROTECTED]> said:
monotone> Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> writes:
monotone>
monotone> > Speaking of formats, I find it a bit surprising that the
monotone> > revision for a merge only sho
This is a bit of an edge case :-)
I understand that on the bleeding edge, monotone log doesn't show
merges any more. In some cases, the result is a bit... interesting!
] : ; monotone-0.26pre1 log -r 817eddb284f82ffb8b4b5db11540f69495e4d64e --last=1
]
Nathaniel Smith <[EMAIL PROTECTED]> writes:
> On Thu, Jan 12, 2006 at 01:58:16PM +, Bruce Stephens wrote:
[...]
>> So how about a variant of get_revision_cert_trust which is only called
>> on things which are heads and which gives a final determination, given
>> all the certs attached to a r
On Thu, Jan 12, 2006 at 11:37:52PM +, Bruce Stephens wrote:
> It's kind of how we do things at work: we use a CVS repository
> together with scripts which commit multiple files more or less at
> once, but before committing, we send out proposed changes to one or
> two people for review.
>
>
Thinking more about it, and discussing it on IRC, I'm now wondering
what the reasoning behind making log skip merges by default was.
It seems to me like the benefit for users isn't that great and, as
shown in my previous message, can be a bit confusing. It seems to me
that this change really bene
Daniel Carosone <[EMAIL PROTECTED]> writes:
> On Thu, Jan 12, 2006 at 11:37:52PM +, Bruce Stephens wrote:
[...]
>> So I'm imagining how we might work using some other system. Our
>> way of working tends to involve using CVS working copies as
>> distributed branches, and we email patches for
Hi all,
I've been out of the monotone loop for quite a while again, but I just
noticed that Nathaniel is going to be presenting at CodeCon in San
Francisco this February. I'll be there for the show, and would like to
offer to buy any monotone developers who are interested a beer (or
beverage of y
23 matches
Mail list logo
