On a slightly related note...
Is there a version of the fossil logo GIF (Home screen) with a transparent
background?
For dark themes like this, I think it would look better than the block of
stark white currently shown.
On 13 January 2018 at 06:27, Antoine Chavasse wrote:
> Thanks, I fixed this
Here is a script I must have stolen from this mailing list a long time ago.
If someone can give me the attribution details, I'll update the gist.
https://gist.github.com/dahu/a5fce430f8045d1f87da9fc74ab46f70
On 6 August 2017 at 16:06, abhijit nandy wrote:
> I need to create quite a few reposi
This is already possible with pathed globs in your
.fossil-settings/ignore-glob file.
On 19 April 2017 at 01:10, David Mason wrote:
> I have had to use Git for something this semester. It was mostly a
> failure and I'll find a way to use fossil going forward.
>
> That said, I noticed one featur
On 15 October 2016 at 05:26, Steven Gawroriski
wrote:
> On Sat, 15 Oct 2016 05:59:23 +0900
> Osamu Aoki wrote:
>
> > Hi,
> >
> > Here is a trivial patch to build the source tree even with unknown
> > options for autosetup/autosetup but make sure to warn user.
> >
> > The idea is from Barak A. Pe
ort of all check-ins to FILE in one of the following repository
FORMATs:
--fossil the fossil format
--gitthe git-fast-export format
If FILE is not specified or is "-", write export check-ins to standard
output.
On 27 July 2016 at 06:04,
I like the `export` idea. It solves the `trash-can` problem and it's a
feature that has been (directly or indirectly) requested a few times over
the years. That covers (a) and (c), only leaving:
(B) Define the syntax of ARGS.
Let me begin that bikeshed with:
Existing tools:
find . -type f -na
I'm glad to hear that.
On 27 June 2016 at 13:31, Richard Hipp wrote:
> On Mon, Jun 27, 2016 at 7:13 AM, Barry Arthur
> wrote:
> > Any stats on how many we lost during the blackout?
>
> 0. Net number of subscribers is unchanged.
>
>
> --
>
Any stats on how many we lost during the blackout?
On 27 June 2016 at 12:34, Scott Doctor wrote:
> Yay.
>
> -
> Scott Doctor
> sc...@scottdoctor.com
>
>
> On 06/26/2016 21:14, Steve Stefanovich wrote:
>
>> Works, don't touch it anymore :)
>>
>> Cheers,
>> Steve
>> ---
>>
>>
The distributed/shared repository doesn't just hold trunk... it holds all
non-private branches too. So when your developers are ready for you to
review their work, they commit it to their task branch and then you
(remotely) checkout/update to that branch (preferably into a fresh
directory) and test
I was going to suggest an alternative approach being through enhancements
to chiselapp.com - but that is not any better than a mailing list if the
forum content is not stored inside the fossil repo for the associated
project, as was the desire of the OP, iiuc.
On the surface, it sounds appealing t
This is useful. Thanks.
On 23 January 2016 at 03:34, Dewey Hylton wrote:
> In the end I think the sql method is the safest and best bet for my use
> case. This was really quick to cobble together, and of course doesn't have
> any protection (eg. from sql-injection or whatever), but as I'm just
>
If you don't want to pollute your fossil repository with LBFs, you could
use a similar approach to git's lfs solution by storing the actual files in
Dropbox or boar (https://bitbucket.org/mats_ekberg/boar/wiki/Home) and
text-linking to them from within your fossil-managed repo. I haven't tried
eith
My favourite tool for this sort of thing is supercat:
http://supercat.nosredna.net/
I don't know if it compiles on Windows.
On 2 October 2015 at 01:08, Andy Bradford wrote:
> Thus said "Tony Papadimitriou" on Thu, 01 Oct 2015 19:19:55 +0300:
>
> > 1. highlight the whole entry, not just the word
On 13 September 2015 at 02:21, Andy Bradford
wrote:
> Thus said Warren Young on Fri, 11 Sep 2015 18:27:36 -0600:
>
> > Also, it implies that you're asking Fossil to undo changes, modified
> > in some way using diffs.
>
> Fair enough. I only expressed my opinion about where I thought it fit,
>
The latest Fuel 2.0 is also quite usable now.
https://fuel-scm.org/fossil/home
On 10 September 2015 at 05:03, paul wrote:
> On 09/09/15 20:12, j. van den hoff wrote:
>
>> On Wed, 09 Sep 2015 20:19:04 +0200, Ron W wrote:
>>
>> On Wed, Sep 9, 2015 at 7:19 AM, Luca Ferrari
>>> wrote:
>>>
>>>
I keep all my fossils in /mnt/museum/ and then I clone each fossil to
the place it is needed, with a working directory below it. The
/mnt/museum directory is on a separate disk to my working disk, so
with auto-sync I get free backups. Having all fossils in one directory
makes for easier off-box bac
16 matches
Mail list logo
