On 08/01/2016 11:01 PM, Ron W wrote:
> On Mon, Aug 1, 2016 at 8:22 PM, Adam Jensen Is there a way to run these scripts automatically after each checkout?
>
>
> My team and I do this as part of the build procedure. Basically, we
> treat those as part of the "product" being built, so when we d
On 08/01/2016 10:25 PM, Steve Stefanovich wrote:
> At the end, you didn't add the empty-dirs file. You need to do 'fossil add *
> --dotfiles' or explicitly do 'f add .fossil-settings/empty-dirs', then
> commit. Then a subsequent checkout will create the directories.
>
Thanks. Following John's d
On Aug 1, 2016 8:02 PM, "Ron W" wrote:
>
> On Mon, Aug 1, 2016 at 8:22 PM, Adam Jensen wrote:
>>
>> On 08/01/2016 07:40 PM, bch wrote:
>>
>> > in a controlling file. Something like a purpose-built makefile or
>> > script that handles this layout, so that -it- can be versioned in
>> > fossil; foss
On Mon, Aug 1, 2016 at 8:22 PM, Adam Jensen wrote:
> On 08/01/2016 07:40 PM, bch wrote:
>
> > in a controlling file. Something like a purpose-built makefile or
> > script that handles this layout, so that -it- can be versioned in
> > fossil; fossil wasn't/isn't currently designed to handle that s
At the end, you didn't add the empty-dirs file. You need to do 'fossil add *
--dotfiles' or explicitly do 'f add .fossil-settings/empty-dirs', then commit.
Then a subsequent checkout will create the directories.
S.
Original Message
From: Adam Jensen
Sent: Tuesday, 2 August 2016 10:02
To: foss
On 08/01/2016 07:40 PM, bch wrote:
> There has been lots of discussion about this over the years
> (https://www.google.ca/search?q=fossil-users+empty+directory).
>
> I personally handle this (and other metadata things like user:group
> ownership or permissions (though we now handle --x (executable
On 08/01/2016 07:25 PM, Steve Stefanovich wrote:
>
> Create a .fossil-settings directory in the root of your checkout, and in it
> add empty-dirs file with relative paths to where you want empty directories
> created, fossil add/commit.
>
Is there documentation for that approach? I can't seem
There has been lots of discussion about this over the years
(https://www.google.ca/search?q=fossil-users+empty+directory).
I personally handle this (and other metadata things like user:group
ownership or permissions (though we now handle --x (executable bit))
in a controlling file. Something like
Create a .fossil-settings directory in the root of your checkout, and in it
add empty-dirs file with relative paths to where you want empty directories
created, fossil add/commit.
Cheers,
Steve
---
From: Adam Jensen
Sent: Tuesday, 2 August 2016 09:19
To: fossil-users@lists.fossil-scm.org
Repl
On 8/1/16, Adam Jensen wrote:
> Is there a way to
> commit empty directories to the repository so the project's directory
> structure can be preserved and reconstructed?
No, sadly, there is not. Fossil versions only files. Directories
exist only if they contain a file.
--
D. Richard Hipp
d..
Hi,
I haven't before used fossil to manage a project. Is there a way to
commit empty directories to the repository so the project's directory
structure can be preserved and reconstructed?
Actually, some of the directories aren't empty but rather their contents
are ignored:
fsl add --ignore '*.db
Hi David,
Thanks for fixing and pushing it.
With regards,
Kain
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>> Yet another small "problem". The C compiler with -std switch complains
>> about the comment style in file src/attach.c:91:
>>
http://www.fossil-scm.org/fossil/artifact/3d0f4416538b9154333fba4717670584669bf9eb?txt=1&ln=91
On Mon, Aug 1, 2016 at 8:37 AM, David Vines
wrote:
> The comment style pr
13 matches
Mail list logo