[Monotone-devel] Re: Dumb Question

2006-07-12 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timothy Brownawell schreef: > On Wed, 2006-07-12 at 12:20 -0700, Rob Schoening wrote: >> Is there a recommended way to roll a particular file or files back to >> a particular revision? "mtn update" affects the entire workspace, >> which I don't want.

[Monotone-devel] Re: Dumb Question

2006-07-12 Thread Bruce Stephens
Koen Kooi <[EMAIL PROTECTED]> writes: > Timothy Brownawell schreef: >> On Wed, 2006-07-12 at 12:20 -0700, Rob Schoening wrote: >>> Is there a recommended way to roll a particular file or files back to >>> a particular revision? "mtn update" affects the entire workspace, >>> which I don't want. O

[Monotone-devel] Re: Dumb Question

2006-07-12 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bruce Stephens schreef: > Koen Kooi <[EMAIL PROTECTED]> writes: > >> Timothy Brownawell schreef: >>> On Wed, 2006-07-12 at 12:20 -0700, Rob Schoening wrote: Is there a recommended way to roll a particular file or files back to a particular r

[Monotone-devel] Re: Dumb Question

2006-07-13 Thread Bruce Stephens
Nathaniel Smith <[EMAIL PROTECTED]> writes: > On Wed, Jul 12, 2006 at 09:49:13PM +0100, Bruce Stephens wrote: >> A restrictions version of "pluck" would do much what I imagine you'd >> expect "update" to do. I suspect that would be easily accepted and >> understood by users. > > Committed to main

[Monotone-devel] Re: Dumb Question

2006-07-13 Thread Steven E. Harris
Nathaniel Smith <[EMAIL PROTECTED]> writes: > Other VCSes have historically overloaded the 'update' command, so it > performed a bunch of logically unrelated functions -- moving your > work in progress, doing merges, reverting files, you name it. Does "mtn update" merge changes into files modifie

[Monotone-devel] Re: Dumb Question

2006-07-13 Thread Steven E. Harris
Timothy Brownawell <[EMAIL PROTECTED]> writes: > Yes. Good; that's what I thought. I was confused by Nathaniel Smith's comparison of monotone's simple 'update' with the more complex command in other tools. -- Steven E. Harris ___ Monotone-devel ma

Re: [Monotone-devel] Re: Dumb Question

2006-07-12 Thread Jeronimo Pellegrini
On Wed, Jul 12, 2006 at 09:38:58PM +0200, Koen Kooi wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Timothy Brownawell schreef: > > On Wed, 2006-07-12 at 12:20 -0700, Rob Schoening wrote: > >> Is there a recommended way to roll a particular file or files back to > >> a particular revi

Re: [Monotone-devel] Re: Dumb Question

2006-07-12 Thread Bruce Stephens
Koen Kooi <[EMAIL PROTECTED]> writes: [...] > In an ideal gui one would use revert -r to go back in ancestry > and update -r to walk down the family tree. Maybe. I think this use of revert was intended to allow arbitrary , so it would work forwards and backwards (and sideways). > Anyway, if mo

Re: [Monotone-devel] Re: Dumb Question

2006-07-12 Thread Nathaniel Smith
On Wed, Jul 12, 2006 at 09:38:58PM +0200, Koen Kooi wrote: > Timothy Brownawell schreef: > > On Wed, 2006-07-12 at 12:20 -0700, Rob Schoening wrote: > >> Is there a recommended way to roll a particular file or files back to > >> a particular revision? "mtn update" affects the entire workspace, > >

Re: [Monotone-devel] Re: Dumb Question

2006-07-12 Thread Nathaniel Smith
On Wed, Jul 12, 2006 at 09:49:13PM +0100, Bruce Stephens wrote: > A restrictions version of "pluck" would do much what I imagine you'd > expect "update" to do. I suspect that would be easily accepted and > understood by users. Committed to mainline last week. Rather an overcomplicated interface

Re: [Monotone-devel] Re: Dumb Question

2006-07-12 Thread Nathaniel Smith
On Wed, Jul 12, 2006 at 10:25:50PM +0200, Koen Kooi wrote: > In an ideal gui one would use revert -r to go back in ancestry and > update -r to walk down > the family tree. > Anyway, if monotone can do 'update -r' it should be able to > 'update' files in a > similiar command, otherwise users could

Re: [Monotone-devel] Re: Dumb Question

2006-07-12 Thread Rob Schoening
I wouldn't change anything.  This whole thread is, as you say, a documentation issue.   Which brings me to my next question:   There does not seem to be an FAQ on the Monotone Wiki.  Would you be averse if I started one and copied the contents of the existing FAQ in there?  Or is there a good reaso

Re: [Monotone-devel] Re: Dumb Question

2006-07-13 Thread Timothy Brownawell
On Thu, 2006-07-13 at 11:03 -0700, Steven E. Harris wrote: > Nathaniel Smith <[EMAIL PROTECTED]> writes: > > > Other VCSes have historically overloaded the 'update' command, so it > > performed a bunch of logically unrelated functions -- moving your > > work in progress, doing merges, reverting fi

Re: [Monotone-devel] Re: Dumb Question

2006-07-13 Thread Nathaniel Smith
On Thu, Jul 13, 2006 at 12:19:16PM -0700, Steven E. Harris wrote: > Timothy Brownawell <[EMAIL PROTECTED]> writes: > > > Yes. > > Good; that's what I thought. I was confused by Nathaniel Smith's > comparison of monotone's simple 'update' with the more complex command > in other tools. Ah, I jus

FAQ on wiki (was Re: [Monotone-devel] Re: Dumb Question)

2006-07-13 Thread Nathaniel Smith
On Wed, Jul 12, 2006 at 11:53:17PM -0700, Rob Schoening wrote: >Which brings me to my next question: > >There does not seem to be an FAQ on the Monotone Wiki. Would you be >averse if I started one and copied the contents of the existing FAQ in >there? Or is there a good reason th

Re: FAQ on wiki (was Re: [Monotone-devel] Re: Dumb Question)

2006-07-13 Thread Daniel Carosone
On Thu, Jul 13, 2006 at 12:16:15AM -0700, Nathaniel Smith wrote: > OTOH, while the manual is kept up to date at all times, I think the > last time the FAQ was _updated_ also predates the wiki by a > considerable amount. It's quite inaccurate or out of date, and > embarassing. I don't see how putt

Re: FAQ on wiki (was Re: [Monotone-devel] Re: Dumb Question)

2006-07-13 Thread Nathaniel Smith
On Thu, Jul 13, 2006 at 05:24:16PM +1000, Daniel Carosone wrote: > On Thu, Jul 13, 2006 at 12:16:15AM -0700, Nathaniel Smith wrote: > > OTOH, while the manual is kept up to date at all times, I think the > > last time the FAQ was _updated_ also predates the wiki by a > > considerable amount. It's