On 11/05/2017 16:14, 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
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
>
> 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
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
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
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
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
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
] Problem with: fossil revert -r xxx
On 5/11/17, Ross Berteig <r...@cheshireeng.com> 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 fac
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
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
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
On 5/10/2017 8:54 PM, 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".
The help also says
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".
This is with fossil 2.2 [81d7d3f43e] 2017-04-11 20:54:55 UTC
*Ron
14 matches
Mail list logo