That worked. According to the changes command, 136 history files
removed, 81 new history files added, and 22 files were edited.
The commit completed without error this time. So I guess I will
make a batch file to do those three commands for when I do a commit.
-
Scott
On 3/26/18, Scott Doctor wrote:
> I ran the stash command and got the following:
>
> no such file: D/water/C/slave/__history/main.c.~15~
Probably this mean that you previously committed the file main.c.~15~
but it was subsequently deleted without you doing "fossil rm".
If you want to check-in an
I ran the stash command and got the following:
no such file: D/water/C/slave/__history/main.c.~15~
I am writing code for several Atmel (now Microchip) sam4s Arm
processora using Atmel Studio IDE. This is built on Microsloths
Visual Studio. The system automatically makes many history
sub-folde
On Mar 26, 2018, at 1:27 PM, Scott Doctor wrote:
>
> aborting due to prior errors
I’ve seen that sort of message on “fossil update” when a local file is marked
read-only and the file was changed on the remote system.
Obviously that is not exactly what is happening here, but the broader point i
On 3/26/18, Scott Doctor wrote:
>
> I just typed:
>
> fossil commit
>
> All I wanted to do was take a snapshot of the current state in
> case I wanted to back out of my changes after my forthcoming
> edit session. Am I doing this wrong?
You seem to be doing it right. I don't know what the proble
I just typed:
fossil commit
All I wanted to do was take a snapshot of the current state in
case I wanted to back out of my changes after my forthcoming
edit session. Am I doing this wrong?
-
Scott Doctor
[email protected]
-
On 3/26/2018
On 26 March 2018 at 12:27, Scott Doctor wrote:
>
> A while back I created a new repository for a project I ressurected. Checked
> it after creating with the fossil ui that all files included and such.
> Everything OK.
>
> My project contains many folders and a couple hundred files for a multi
> pr
On 3/26/18, Scott Doctor wrote:
> That is the entirety of the error message. Such is the problem I
> am having trying to find what is the error. The error message
> displayed, then returned to the command line prompt
OK. Without seeing the output, I can't suggest much. But perhaps you
could try
I emailed you the _FOSSIL_ file for the repository
-
Scott Doctor
[email protected]
-
On 3/26/2018 12:42, Richard Hipp wrote:
On 3/26/18, Scott Doctor wrote:
A bunch of file names scrolled up the screen then got the message:
aborting due to
That is the entirety of the error message. Such is the problem I
am having trying to find what is the error. The error message
displayed, then returned to the command line prompt
-
Scott Doctor
[email protected]
-
On 3/26/2018 12:42, Richard
On 3/26/18, Scott Doctor wrote:
>
> A bunch of file names scrolled up the screen then got the message:
>
> aborting due to prior errors
>
More details on the error message would be helpful.
--
D. Richard Hipp
[email protected]
___
fossil-users mailing li
11 matches
Mail list logo
