Timothy Brownawell [EMAIL PROTECTED] writes:
On Sat, 2006-09-09 at 20:51 +0200, Wim Oudshoorn wrote:
SCENARIO I: Non project leader commits to branch FOO.Stable
Expected behaviour:
This commit should not by default be
On Sun, 2006-09-10 at 08:44 +0200, Wim Oudshoorn wrote:
Timothy Brownawell [EMAIL PROTECTED] writes:
SCENARIO III: A project leader leaves
-
Expected behaviour:
The new or remaining project leader can revoke
the 'commit' rights
Nathaniel Smith schrieb:
Another possibility in this particular case would be automate update
simply require that the caller provide the target revision; then this
error can't happen. Instead, the caller would go to get the target
for the update, discover there were multiple candidates, and
Daniel Carosone schrieb:
Would an 'automate' locale/translation, with machine-friendly messages
like this, be unreasonable?
I'd vote for that, definitely.
Thomas.
--
- I know that I don't know. (Sokrates)
Guitone, a frontend for monotone: http://guitone.berlios.de
Music lyrics and more:
Timothy Brownawell schrieb:
Probably, yes. I don't really think that's the kind of thing gettext is
designed for. (Also, AIUI, using gettext would require that you actually
*install* monotone, so the translation files get put in the right place.
Probably not a nice thing to require for making
On Sun, Sep 10, 2006 at 12:34:56PM +1000, Daniel Carosone wrote:
Would an 'automate' locale/translation, with machine-friendly messages
like this, be unreasonable?
Aside from being insane, I think it isn't possible -- you can't just
use arbitrary strings for locales, at least on some systems
(For archive readers: this should be read after
http://article.gmane.org/gmane.comp.version-control.monotone.devel/8169
)
The policy branch framework has a chicken-and-egg problem; we want the
trust rules in effect at any given time to be something like those
written in the head of the policy
On Sun, Sep 10, 2006 at 10:00:11AM +0200, Thomas Keller wrote:
Nathaniel Smith schrieb:
Another possibility in this particular case would be automate update
simply require that the caller provide the target revision; then this
error can't happen. Instead, the caller would go to get the target
Nathaniel Smith [EMAIL PROTECTED] writes:
(For archive readers: this should be read after
http://article.gmane.org/gmane.comp.version-control.monotone.devel/8169
)
Another try
---
Here's an algorithm that does work:
Call a revision R with cert C trivially reachable from some
On Sun, 2006-09-10 at 14:01 +0200, Wim Oudshoorn wrote:
Nathaniel Smith [EMAIL PROTECTED] writes:
(For archive readers: this should be read after
http://article.gmane.org/gmane.comp.version-control.monotone.devel/8169
)
Another try
---
Here's an algorithm that does
Timothy Brownawell [EMAIL PROTECTED] writes:
Oh, and I don't like the fact that everyone who ever had commit
access could always stall the project.
I want that if I distrust Mallory, that all revisions signed
by him will NOT enter my database.
There are different levels of
Nathaniel Smith [EMAIL PROTECTED] writes:
[...]
However, consider an antagonistic fork:
A -- states that Alice and Mallory have commit access
|
B -- states that only Alice has commit access; signed by
| Alice
C -- states that only Mallory has commit
On Sun, Sep 10, 2006 at 02:01:12PM +0200, Wim Oudshoorn wrote:
Nathaniel Smith [EMAIL PROTECTED] writes:
Call a revision R with cert C trivially reachable from some other
revision S, if R is a descendent of S, and C is a cert trusted by S
which claims that R is in the policy branch.
Nathaniel Smith [EMAIL PROTECTED] writes:
[...]
Right, this is the same algorithm, except that you only consider
jumping from a revision to its immediate children, as opposed to all
descendents. One can do things this way; the only reason I didn't
suggest doing it that way is that it
Nathaniel Smith [EMAIL PROTECTED] writes:
On Sun, Sep 10, 2006 at 02:01:12PM +0200, Wim Oudshoorn wrote:
Nathaniel Smith [EMAIL PROTECTED] writes:
Call a revision R with cert C trivially reachable from some other
revision S, if R is a descendent of S, and C is a cert trusted by S
which
Hi Nathaniel,
Sorry, your mail was filtered into my Monotone mailbox instead of my
Botan one, and so got to spend some time in email purgatory. The fix
you're looking for was made in 1.4.12, the specific patch being:
--- Botan-1.4.10/src/out_buf.cpp2005-12-18 17:19:29.0 -0500
On Sun, Sep 10, 2006 at 04:53:11PM -0400, Jack Lloyd wrote:
Hi Nathaniel,
Sorry, your mail was filtered into my Monotone mailbox instead of my
Botan one, and so got to spend some time in email purgatory. The fix
you're looking for was made in 1.4.12, the specific patch being:
Whoops,
On Sun, Sep 10, 2006 at 02:16:17PM -0700, Nathaniel Smith wrote:
Whoops, right, Matt found that actually -- sorry, I forgot to send a
followup.
No problem, glad you weren't blocking on my response.
I'm still curious, if you have the time, about the bespoke heap
management... do we know
On Sun, Sep 10, 2006 at 02:45:28AM -0700, Nathaniel Smith wrote:
On Sun, Sep 10, 2006 at 12:34:56PM +1000, Daniel Carosone wrote:
Would an 'automate' locale/translation, with machine-friendly messages
like this, be unreasonable?
Aside from being insane, I think it isn't possible
Oh well,
On Mon, 2006-09-11 at 13:08 +1000, Daniel Carosone wrote:
On Sun, Sep 10, 2006 at 02:45:28AM -0700, Nathaniel Smith wrote:
On Sun, Sep 10, 2006 at 12:34:56PM +1000, Daniel Carosone wrote:
Would an 'automate' locale/translation, with machine-friendly messages
like this, be unreasonable?
20 matches
Mail list logo
