On Wed, Jun 15, 2016 at 09:02:54PM -0500, lvh wrote:
> I’m interested in exploring the possibilities of moving to a Fossil
> monorepo at $dayjob. One of the things I’m not sure how to deal with
> appropriately is dealing with projects managed upstream in some other
> VCS (which, de facto, appears
On 16 Jun 2016, at 04:02 , lvh <_...@lvh.io> wrote:
> I’m interested in exploring the possibilities of moving to a Fossil monorepo
> at $dayjob. One of the things I’m not sure how to deal with appropriately is
> dealing with projects managed upstream in some other VCS (which, de facto,
>
On Wed, Jun 15, 2016 at 10:02 PM, lvh <_...@lvh.io> wrote:
>
> These are important to the software we’re building, so they ought to live
> in VCS, or at least a reference to them should. How do you manage this?
> Just put the .git dir in version control? Bare checkout? Something that
> references
Hello,
there is 'project_name', but no 'project_description'.
++
https://www.fossil-scm.org/index.html/artifact/827386e6fd0ca33d52f7a663c3c45edde4df1e9a?txt=1=156
my ??
--
https://www.juef.tk/
signature.asc
Description: PGP signature
___
(Thu, 16 Jun 07:05) Svyatoslav Mishyn:
> Now I use simply index.html and update it manually.
Of course not manually ;)
make-index.sh:
#!/bin/sh
cat index.html.pre > index.html
printf "\n\t\t\n" >> index.html
for f in /home/juef/fossil/*.fossil; do
printf "\t\t\t\n\t\t\t\t%s
5 matches
Mail list logo
