There was some discussion in past about compiling fossil for Android.
Is it still alive?
Is there any .apk available?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Hello,
$ fossil all changes
Changes for ??? at /home/michai/proj/046/:
EDITED db/parts.txt
EDITED db/supplieritems.txt
What was supposed to be in place of the '???' ?
Michai
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http:/
On Mon, Jun 16, 2014 at 7:21 AM, Michai Ramakers
wrote:
> Hello,
>
> $ fossil all changes
> Changes for ??? at /home/michai/proj/046/:
> EDITED db/parts.txt
> EDITED db/supplieritems.txt
>
> What was supposed to be in place of the '???' ?
>
The "Project Name" that you set on the top line
On 16 June 2014 13:29, Richard Hipp wrote:
>
> On Mon, Jun 16, 2014 at 7:21 AM, Michai Ramakers
> wrote:
>>
>> $ fossil all changes
>> Changes for ??? at /home/michai/proj/046/:
>> EDITED db/parts.txt
>> EDITED db/supplieritems.txt
>>
>> What was supposed to be in place of the '???' ?
>
>
Hi Urmil,
actually there is an apk for fossil, though it only supports serving
repos AFAIR.
https://play.google.com/store/apps/details?id=es.dadbiz.fossil
I used it often to backup my repos to my phones sd-card and it worked
out quite well.
Am 16.06.2014 12:02, schrieb Urmil Parikh:
The
On Sat, Jun 14, 2014 at 4:02 PM, wrote:
> 2. Can a branch contain only the single incomplete file I'm working on,
> but somehow to 'load' this branch together with the 'trunk'? I.e., I want
> to have all the files of the current trunk plus the single (or few) file(s)
> of my special WIP branch.
Hi, all,
This is for Unix-shell users only (including workalikes on Windows)...
Here's a time-saving tip which i use very often myself, but most CLI users
i know don't seem to know about:
It often happens that i'm typing a commit message when i decide i need to
stop and go check if what i'm typi
Hi,
I just want to share some feedback, for fun I tried to convert some of
the FreeBSD repositories to fossil to see how it performs
I first tried the FreeBSD Documentation repository, to go the easy way
I took the FreeBSD git mirror (https://github.com/freebsd/freebsd-doc
and run
git fast-export
On Mon, Jun 16, 2014 at 2:24 PM, Stephan Beal wrote:
> Hi, all,
>
> This is for Unix-shell users only (including workalikes on Windows)...
>
> Here's a time-saving tip which i use very often myself, but most CLI users
> i know don't seem to know about:
>
> It often happens that i'm typing a commi
Under bash another way to achieve the goal of temporarily putting your
partially written commit command aside is to do: ^a ^k
This puts your command in the cut buffer. To retrieve it (after having run
fossil gdiff to figure out what you did!) just do: ^y
On Mon, Jun 16, 2014 at 1:24 PM, Stephan
Remember that the buffer is only one level deep, though. A subsequent ^W,
^K , etc will clobber the previous contents.
Along lines of Stephan Beals method, I use ":" preceding the fossil
command. So:
$ : fossil ci -m 'some msg'
("$" is shell prompt).
":" is a command that consumes it's argument
On Mon, Jun 16, 2014 at 11:49 PM, B Harder wrote:
> Remember that the buffer is only one level deep, though. A subsequent ^W, ^K
> , etc will clobber the previous contents.
>
> Along lines of Stephan Beals method, I use ":" preceding the fossil command.
> So:
>
> $ : fossil ci -m 'some msg'
>
> ("
12 matches
Mail list logo
