On 31 December 2012 15:53, Edward Berner e...@bernerfam.com wrote:
fossil info calls it project-code but it seems to be the same thing
that fossil new and fossil clone call project-id.
Waitwhat? My version of Fossil (This is fossil version 1.25 [558a17a686]
2012-12-22 13:48:31 UTC) doesn't
On 31 December 2012 17:27, Edward Berner e...@bernerfam.com wrote:
Waitwhat? My version of Fossil (This is fossil version 1.25 [558a17a686]
2012-12-22 13:48:31 UTC) doesn't show anything about project-id for
fossil new/clone.
What do you get when you create a test repository? It should, I
You should have set your check-in date to something ridiculously early.
(One of the options when creating the repo for pushing.) Since you didn't,
shun instead the initial check-in. When I did that to my hosted app it
worked fine.
On 17 February 2013 22:09, jim Schimpf jim.schi...@gmail.com
On 21 February 2013 04:57, Lluís Batlle i Rossell vi...@viric.name wrote:
1) there were a way to clone+checkout at once into a subdirectory:
fossil clonedir http://blabla.org/ blabla
# ^ It creates blabla/, blabla/.repository.fossil, and in it, checks out
# the .repository.fossil, for
On 15 August 2013 21:23, John Long codeb...@inbox.lv wrote:
Hi, is it possible to ignore UNIX executables? I want to do an addr on a
directory tree but I don't know how to tell fossil not to track the
binaries
since they have no naming pattern. Until now I've been living with it but
it
is
On 15 August 2013 21:23, John Long codeb...@inbox.lv wrote:
Hi, is it possible to ignore UNIX executables? I want to do an addr on a
directory tree but I don't know how to tell fossil not to track the
binaries
since they have no naming pattern. Until now I've been living with it but
it
is
Where do I find the variables and commands Fossil exposes to TH documented?
--
Perhaps people don't believe this, but throughout all of the discussions
of entering China our focus has really been what's best for the Chinese
people. It's not been about our revenue or profit or whatnot.
--Sergey
On 27 July 2014 11:04, Eric Rubin-Smith eas@gmail.com wrote:
Fossil *could* support export to JIRA+git in particular, for example, by
providing a tool that (a) exports to JIRA's supported JSON import format,
(b) collects the mapping from the fossil ticket IDs to the JIRA ticket
IDs, then
The key wording there is *within the repository* tree.
It doesn't change the file system, only the naming of the files, etc. in
the repository. Whether this is desired or correct behaviour is … an area
of frequent discussion.
My own response to that discussion is to use the fsl wrapper (
Here I go again reminding people that if you just want short versions of
commands, aliases for common command operations with specific switches,
etc. that http://fossil.0branch.com/fsl/home has a solution for this
already that's been available for years now.
On 26 February 2016 at 10:57, Ross
I know that every time I mention this I get silently, perhaps even
hostilely, ignored, but really guys, why not just use fsl for your
customization needs? Colourizing output is in the cookbook:
http://fossil.0branch.com/fsl/wiki?name=Cookbook, along with lots of other
nifty tricks like aliasing,
se fsl wrapper as a standard filter?
>
> You can get a sense of what the repo extension does from this wiki page:
> http://chiselapp.com/user/kiatoa/repository/fsl/wiki?name=Usage
>
> Thanks,
>
> Matt
> -=-
>
> On Mon, Apr 25, 2016 at 7:48 AM, Michael Richter <ttm
Platform: Windows 10.
Fossil version: 1.34 [62dcb00e68]
After making a few changes to a project (IAR Embedded Workbench for ARM)
and committing them on a feature branch, I tried to check out the main
development branch. The result was a hard crash. My repository is now in
a state where I can't
Trying to open the same repository under a Linux system (fossil version
1.33 [5b456cfa6b]) gives me this: "[1]9388 segmentation fault fossil
open /path/to/Joystick.fossil"
On 15 April 2016 at 11:31, Michael Richter <ttmrich...@gmail.com> wrote:
> Platform: Windows 10.
>
New_Version:
0d481726efdeaf7e1e425da5db82af9042217eaa59ca689e3a253cefdbb93a77
ERROR: [CPU/STM32F103RC_buildnumber] is different on disk compared to the
repository
NOTICE: Repository version of [CPU/STM32F103RC_buildnumber] stored in
[file-61e47e1f48a9c5ea]
ERROR: [CPU/STM32L051C8_buildnumber] is
it.
On Thu, 9 May 2019 at 09:30, Michael Richter wrote:
> New_Version:
> 0d481726efdeaf7e1e425da5db82af9042217eaa59ca689e3a253cefdbb93a77
> ERROR: [CPU/STM32F103RC_buildnumber] is different on disk compared to the
> repository
> NOTICE: Repository version of [CPU/STM32F103RC_buildnumber] st
101 - 116 of 116 matches
Mail list logo
