Re: [fossil-users] Problem with: fossil revert -r xxx

I'm on the road and may not be thinking clearly, but if you're trying to revert your entire tree to the state 6 or 7 commits ago, might it be easier to update to the commit you want, rename the first commit in the now unwanted branch, and continue on from the new root? -- Scott Robison

Re: [fossil-users] autosetup v0.6.6 issue

On 5/11/2017 2:48 PM, Sergei Gavrikov wrote: $ echo ./configure ... | sed 's/--with-[^[:space:]]\+/&=1/g' | sh Problem is --with-openssl=/local/ssl doesn't fit that pattern. Nor does --with-zlib which also takes a variety of string values. I don't see why the author of autosetup

Re: [fossil-users] autosetup v0.6.6 issue

On Fri, 12 May 2017, Sergei Gavrikov wrote: Temp. solution for my set of --with-* options is $ echo configure ... | sed 's/--with-\w\+/&=1/g' | sh To err is human $ echo ./configure ... | sed 's/--with-[^[:space:]]\+/&=1/g' | sh Sergei ___

Re: [fossil-users] autosetup v0.6.6 issue

Temp. solution for my set of --with-* options is $ echo configure ... | sed 's/--with-\w\+/&=1/g' | sh Sergei ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] autosetup v0.6.6 issue

Looks like this was broken as part of a change in handling of boolean options to autosetup. Older versions understood --enable-x and --disable-x, but in a change committed on 2016-09-11, --with-x, and --without-x were added to the list of magic prefixes.

Re: [fossil-users] Problem with: fossil revert -r xxx

> > But in my experience, fossil revert is a rarely used command. > Both `fossil revert afile -r ver` and `fossil update ver afile` seem to be a synonymous way to fetch a file's revision. HOWEVER, there's an important distinction, `fossil update` would __merge-in uncommitted changes__ with the

[fossil-users] autosetup v0.6.6 issue

Hi, It seems that new autosetup [c5e4100705] cannot handle properly configure options with prefixes (enable|disable|with|without). Try, please $ ./configure --with-th1-docs Host System...x86_64-unknown-linux-gnu Build System...x86_64-unknown-linux-gnu C compiler...ccache cc -g -O2

Re: [fossil-users] Problem with: fossil revert -r xxx

On May 11, 2017, at 5:03 AM, Richard Hipp wrote: > > On 5/11/17, Ross Berteig wrote: >> On 5/10/2017 8:54 PM, Ron Aaron wrote: >>> >>> I tried to revert to a good revision 'xxx' using "fossil revert -r xxx" >> >> But in my experience, fossil revert is a

Re: [fossil-users] Limiting cruft in my repos

On May 10, 2017, at 6:40 PM, David Mason wrote: > > On 10 May 2017 at 17:05, Artur Shepilko wrote: > Not sure about the objectives the students are learning in this > course, but if it in any way relates to programming, recognizing as > to what to keep

Re: [fossil-users] Problem with: fossil revert -r xxx

Thus said Ross Berteig on Wed, 10 May 2017 21:35:12 -0700: > But in my experience, fossil revert is a rarely used command. I use revert quite frequently to abandon changes I don't want anymore. I don't often use it with -r though. Andy -- TAI64 timestamp: 400059146dec

Re: [fossil-users] Problem with: fossil revert -r xxx

On Thu, May 11, 2017 at 09:14:43AM -0400, Richard Hipp wrote: > On 5/10/17, Ron Aaron wrote: > > I tried to revert to a good revision 'xxx' using "fossil revert -r xxx" > > > > Despite the help stating "Revert all files if no file name is provided", > > instead fossil told

Re: [fossil-users] Problem with: fossil revert -r xxx

On 5/10/17, Ron Aaron wrote: > I tried to revert to a good revision 'xxx' using "fossil revert -r xxx" > > Despite the help stating "Revert all files if no file name is provided", > instead fossil told me, "the --revision option does not work for the > entire tree". Amid all

Re: [fossil-users] Problem with: fossil revert -r xxx

On 2017-05-11 7:03, Richard Hipp wrote: Yeah. In fact, I didn't even remember that there was a 'revert' command. And even now, I'm not entirely clear what it does, or what it is intended to do. I use it a few times a year when I thoroughly mess up a file or two locally and need to go back

Re: [fossil-users] Problem with: fossil revert -r xxx

Hmm, I happen to use the REVERT command *all* the time. It's the simplest (and possibly only direct) way I know to quickly abort all changes (after experimenting with code) and go back to what was the check-in. How do the rest of you do an abort? I must admit I very rarely used the -r

Re: [fossil-users] Problem with: fossil revert -r xxx

On Thu, May 11, 2017 at 12:17:44PM +0300, Ron Aaron wrote: > Sorry, but I can't see how the terminology "... all files if no file > name is provided" could mean anything but what I assumed. > > It may not be used often, but in the event were one has decided, as I > did, that a certain number of

Re: [fossil-users] Problem with: fossil revert -r xxx

On 5/11/17, Ross Berteig wrote: > On 5/10/2017 8:54 PM, Ron Aaron wrote: >> >> I tried to revert to a good revision 'xxx' using "fossil revert -r xxx" > > But in my experience, fossil revert is a rarely used command. > Yeah. In fact, I didn't even remember that there was a

Re: [fossil-users] Problem with: fossil revert -r xxx

Sorry, but I can't see how the terminology "... all files if no file name is provided" could mean anything but what I assumed. It may not be used often, but in the event were one has decided, as I did, that a certain number of trunk changes (as in: the last 7) need to be reverted, it is what one