On Fri, Nov 21, 2014 at 12:49 AM, Christopher M. Fuhrman wrote:
> So this brings the following question: Is there anyway from the command
> line I can tell fossil that the starting commit is the start of a new
> branch 'trunk' that propagates? Remember, I can't use the UI to do this.
>
In theor
On Fri, Nov 21, 2014 at 11:13 AM, Robert Engelhardt <
m...@robert-engelhardt.de> wrote:
> Hello all,
>
> I'm compiling fossil under Windows 8.1 with gcc 4.9.1 (x64-native).
> Unfortunately check-in [270897a301] broke the build process for me:
>
> When trying to compile compat/zlib/contrib/asm686/m
On Fri, Nov 21, 2014 at 10:14 AM, Robert Engelhardt <
m...@robert-engelhardt.de> wrote:
> I have under version control a directory "A" which was later renamed to
> "a". It contains the files "w", "x", "y" and "z". Although fossil should
> not be case sensitive on Windows (i.e., the respective sett
Hello all,
I'm using fossil 1.30 [45a366a0a0] on Windows. I have the following problem:
I have under version control a directory "A" which was later renamed to
"a". It contains the files "w", "x", "y" and "z". Although fossil should
not be case sensitive on Windows (i.e., the respective settin
Hello all,
I'm compiling fossil under Windows 8.1 with gcc 4.9.1 (x64-native).
Unfortunately check-in [270897a301] broke the build process for me:
When trying to compile compat/zlib/contrib/asm686/match.S, the assembler
bails out with some "invalid instruction suffix" messages. As I found
ou
5 matches
Mail list logo