On Fri, 2006-11-03 at 11:26 +, Ulf Ochsenfahrt wrote:
> Timothy Brownawell wrote:
> > On Sat, 2006-10-28 at 23:57 +0200, Ulf Ochsenfahrt wrote:
> >> Attached is a patch that changes mtn default behavior to add
> >> non-recursively and uses the -R option to reenable old behavior. This
> >> pat
Timothy Brownawell wrote:
> On Sat, 2006-10-28 at 23:57 +0200, Ulf Ochsenfahrt wrote:
>> Attached is a patch that changes mtn default behavior to add
>> non-recursively and uses the -R option to reenable old behavior. This
>> patch makes the add and drop commands more similar.
>
> I've committed
On Sat, 2006-10-28 at 23:57 +0200, Ulf Ochsenfahrt wrote:
> Timothy Brownawell wrote:
> > 'mtn drop -R' is recursive. (hey, we do have a --recursive option. Can
> > we add a --non-recursive and kill --depth?)
>
> Attached is a patch that changes mtn default behavior to add
> non-recursively and
On Tue, Oct 31, 2006 at 08:03:20PM -0800, J Decker wrote:
> I doubt anyone wants "commit ." or "diff ." to be interpreted
> non-recursively (at least without some sort of --non-recursive flag).
> Is this a compelling argument for add/drop to behave the same way?
>
>Is there a fl
I doubt anyone wants "commit ." or "diff ." to be interpreted
non-recursively (at least without some sort of --non-recursive flag).Is this a compelling argument for add/drop to behave the same way?Is there a flag to do this? I wanted to do those, and pluck . to just handle that particular director
On 10/30/06, Nathaniel Smith <[EMAIL PROTECTED]> wrote:
On Sun, Oct 29, 2006 at 11:44:08AM +, Nuno Lucas wrote:
> I believe this is a side effect of renaming from the old dotted ".mtn"
> name, and would consider this a bug, because if people wanted this to
> happen, they would had codded this
On Sun, Oct 29, 2006 at 11:44:08AM +, Nuno Lucas wrote:
> I believe this is a side effect of renaming from the old dotted ".mtn"
> name, and would consider this a bug, because if people wanted this to
> happen, they would had codded this behaviour before.
Err... it was never called ".mtn"; the
In message <[EMAIL PROTECTED]> on Sun, 29 Oct 2006 11:44:08 +, "Nuno Lucas"
<[EMAIL PROTECTED]> said:
ntlucas> I believe this is a side effect of renaming from the old
ntlucas> dotted ".mtn" name, and would consider this a bug, because if
ntlucas> people wanted this to happen, they would had
On Sun, Oct 29, 2006 at 09:55:41AM +0100, Richard Levitte - VMS Whacker wrote:
> In message <[EMAIL PROTECTED]> on Sat, 28 Oct 2006 19:27:18 -0500, Timothy
> Brownawell <[EMAIL PROTECTED]> said:
>
> tbrownaw> I'm not sure we want to change the default, the
> tbrownaw> recursiveness is kinda nice.
On 10/29/06, Julio M. Merino Vidal <[EMAIL PROTECTED]> wrote:
On 10/29/06, Nuno Lucas <[EMAIL PROTECTED]> wrote:
> I believe this is a side effect of renaming from the old dotted ".mtn"
> name, and would consider this a bug, because if people wanted this to
> happen, they would had codded this be
On 10/29/06, Nuno Lucas <[EMAIL PROTECTED]> wrote:
I believe this is a side effect of renaming from the old dotted ".mtn"
name, and would consider this a bug, because if people wanted this to
happen, they would had codded this behaviour before.
This behavior was most likely there before (haven'
On 10/29/06, Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> wrote:
In message <[EMAIL PROTECTED]> on Sat, 28 Oct 2006 19:27:18 -0500, Timothy Brownawell
<[EMAIL PROTECTED]> said:
tbrownaw> I'm not sure we want to change the default, the
tbrownaw> recursiveness is kinda nice.
Yes and no. Ye
In message <[EMAIL PROTECTED]> on Sat, 28 Oct 2006 19:27:18 -0500, Timothy
Brownawell <[EMAIL PROTECTED]> said:
tbrownaw> I'm not sure we want to change the default, the
tbrownaw> recursiveness is kinda nice.
Yes and no. Yes, I love it when it does include all files *when I
want that to happen*
> "Timothy" == Timothy Brownawell writes:
Timothy> I'm not sure we want to change the default, the
Timothy> recursiveness is kinda nice.
For the add operation, I very much dislike it.
Especially when it automatically adds files that I don't want it to
add. I am not sure if monotone
On Sat, 2006-10-28 at 23:57 +0200, Ulf Ochsenfahrt wrote:
> Timothy Brownawell wrote:
> > 'mtn drop -R' is recursive. (hey, we do have a --recursive option. Can
> > we add a --non-recursive and kill --depth?)
>
> Attached is a patch that changes mtn default behavior to add
> non-recursively and
On Sun, 2006-10-29 at 00:37 +0200, Ulf Ochsenfahrt wrote:
[...]
> The passphrase dialog on commit is my biggest problem right now. If the
> passphrase is set in the default monotonerc, then I'd rather just use
> that. If it's not set, I have to ask the user. Jon's original code would
> always as
On Sat, 2006-10-28 at 23:57 +0200, Ulf Ochsenfahrt wrote:
> Timothy Brownawell wrote:
> > 'mtn drop -R' is recursive. (hey, we do have a --recursive option. Can
> > we add a --non-recursive and kill --depth?)
>
> Attached is a patch that changes mtn default behavior to add
> non-recursively and
Nathaniel Smith wrote:
That gives 6 possibilities:
1. no private key, no key set -> error, can't commit
2. no private key, key set -> error, can't commit
3. one private key, no key set -> private key is default
4. one private key, key set -> if both keys are the same, that one is
default, if set
Timothy Brownawell wrote:
> 'mtn drop -R' is recursive. (hey, we do have a --recursive option. Can
> we add a --non-recursive and kill --depth?)
Attached is a patch that changes mtn default behavior to add
non-recursively and uses the -R option to reenable old behavior. This
patch makes the add
On Sat, Oct 28, 2006 at 10:01:29PM +0200, Jon Bright wrote:
> Richard Levitte - VMS Whacker wrote:
> >
> >Then you're using something other than --rccode, aren't you? Because
> >the above basically fulfills the needs of --rccode, as far as I can
> >see.
>
> No. Using stdin to provide the script
On Sat, Oct 28, 2006 at 09:59:35PM +0200, Ulf Ochsenfahrt wrote:
> Hi,
>
> I'll try pasting together the answers from Richard and Timothy.
>
> >- How does monotone select a (default) key to sign?
>
> Richard:
> >If you only have one private key, monotone will choose it (I think, I
> >haven't tes
On Sat, 2006-10-28 at 21:59 +0200, Ulf Ochsenfahrt wrote:
> > - How can I add a directory non-recursively?
>
> Richard:
> > I'm not sure you can. If you want to add specific files in a
> > directory, just add them, the directory itself will be added
> > automagically if needed.
>
> Timothy:
> >
Richard Levitte - VMS Whacker wrote:
Then you're using something other than --rccode, aren't you? Because
the above basically fulfills the needs of --rccode, as far as I can
see.
No. Using stdin to provide the script would be ideal. But if you're
using automate stdio, stdin is already "tak
Hi,
I'll try pasting together the answers from Richard and Timothy.
- How does monotone select a (default) key to sign?
Richard:
If you only have one private key, monotone will choose it (I think, I
haven't tested that for a while).
If _MTN/options has a key identity in it, monotone will cho
In message <[EMAIL PROTECTED]> on Sat, 28 Oct 2006 21:17:11 +0200, Jon Bright
<[EMAIL PROTECTED]> said:
jon> Richard Levitte - VMS Whacker wrote:
jon> >
jon> > Hey bud, check this out (I discovered while looking around the code to
jon> > see how hard it would be to implement --rccode :-)):
jon> >
Richard Levitte - VMS Whacker wrote:
Hey bud, check this out (I discovered while looking around the code to
see how hard it would be to implement --rccode :-)):
: ; echo 'io.stderr:write "FOO!\n"' | mtn heads --rcfile=-
FOO!
mtn: grenen 'net.venge.monotone' har för tillfället ett löv:
970b5cf42
In message <[EMAIL PROTECTED]> on Sat, 28 Oct 2006 20:48:51 +0200, Jon Bright
<[EMAIL PROTECTED]> said:
jon> ...or (as is probably most useful for the plugin), write out some
jon> temporary rc file and use --rcfile. That said, to avoid this
jon> kind of playing with temporary files, it might be
Richard Levitte - VMS Whacker wrote:
ulf> - How can I suppress the automatic commit message dialog and get
ulf> an error instead if no message was given on the command line?
You hack your own edit_comment function in _MTN/monotonerc (works only
with that workspace) or ~/.monotone/monotonerc (
On Sat, 2006-10-28 at 18:23 +0200, Ulf Ochsenfahrt wrote:
> Hi all!
>
> I've got a few questions. Some of these may already have answers, others
> may not. I looked into the manual and checked the monotone built-in
> help, but found no easy answer to these.
>
> - How does monotone select a (def
In message <[EMAIL PROTECTED]> on Sat, 28 Oct 2006 18:23:23 +0200, Ulf
Ochsenfahrt <[EMAIL PROTECTED]> said:
ulf> I've got a few questions. Some of these may already have answers,
ulf> others may not. I looked into the manual and checked the monotone
ulf> built-in help, but found no easy answer t
Hi all!
I've got a few questions. Some of these may already have answers, others
may not. I looked into the manual and checked the monotone built-in
help, but found no easy answer to these.
- How does monotone select a (default) key to sign?
- How can I find out which?
- Why is "automate get_
31 matches
Mail list logo
