On Tue, Jul 11, 2023 at 11:01 AM Sven Schreiber
<sven.schreiber(a)fu-berlin.de> wrote:
Am 11.07.2023 um 14:17 schrieb Cottrell, Allin:
> On Tue, Jul 11, 2023 at 8:11 AM Sven Schreiber
> <sven.schreiber(a)fu-berlin.de> wrote:
>> in my copies/clones of the git repo I'm getting a lot of untracked files
>> which sometimes is a bit annoying. Some of them may have to do with
>> un-recommended builds in the source tree, but others are perhaps more
>> pervasive. I'm not too familiar with the git rules for the .gitignore
>> files: I see there's such a file at the top level, last changed in 2017,
>> and under addons there is a quite recent .gitgnore file added by Artur.
>>
>> Could some knowledgeable person amend these files to cover more of the
>> clutter or noise?
>
> Please give some examples of the files you're talking about.
>
Hm, maybe all those files really are from when I was building inside the
source tree. In a fresh checkout (clone) I couldn't see any even after
doing configure and make in a separate build dir. That's good, of course.
Yeah, I think the current .gitignore works fine. I never see any
untracked files in the gretl source tree, unless they're files I've
put there for some reason or other.
The only remaining question might be whether "make clean"
could or
should be extended to clean up more stuff.
I believe the current status is OK there too. You can do "make
distclean" for a more far-reaching cleanout, but trust me: you don't
want to.
Allin