[PATCH] gitignore: ignore top-level ini files

[Gedare Bloom]

ping: decision needed--should we git-ignore .ini everywhere, .ini in
top-level, or just the default config.ini in top-level?

On Mon, Sep 14, 2020 at 6:51 PM Chris Johns <chrisj at rtems.org> wrote:
>
> On 15/9/20 9:52 am, Gedare Bloom wrote:
> > hah, yes. In rtems.git with the new build system it seems the workflow
> > is to create a .ini file in your top-level source directory to control
> > the build. We should not include those ini files in version control I
> > think?
>
> The INI files do not need to be in the top directory, any valid path should do.
>
> I will let Sebastian decide.
>
> > I meant to start a discussion, then I went for a bicycle ride and forgot.
>
> A ride is more important.
>
> Chris
>
> > -Gedare
> >
> > On Mon, Sep 14, 2020 at 3:47 PM Chris Johns <chrisj at rtems.org> wrote:
> >>
> >> Hi Gedare,
> >>
> >> Which repo is this for? I suspect rtems.git but I thought it best to ask.
> >>
> >> Chris
> >>
> >> On 15/9/20 3:43 am, Gedare Bloom wrote:
> >>> ---
> >>>  .gitignore | 1 +
> >>>  1 file changed, 1 insertion(+)
> >>>
> >>> diff --git a/.gitignore b/.gitignore
> >>> index d7ca74b338..8b28b186e1 100644
> >>> --- a/.gitignore
> >>> +++ b/.gitignore
> >>> @@ -4,6 +4,7 @@ autom4te.cache
> >>>  config.h.in
> >>>  configure
> >>>  doc
> >>> +/*.ini
> >>>  .lock*
> >>>  Makefile.in
> >>>  *.pyc
> >>>