Re: [hackers] [sbase] [PATCH] Add .gitignore

From: Quentin Rameau <quinq_AT_fifth.space>
Date: Mon, 17 Jun 2019 22:44:51 +0200

On Mon, 17 Jun 2019 13:40:47 -0700
Michael Forney <mforney_AT_mforney.org> wrote:

> On 2019-06-17, Quentin Rameau <quinq_AT_fifth.space> wrote:
> >> What's the downside to having it checked into the repository? Are
> >> there any reasons why a user wouldn't want this feature? Personally, I
> >> want it in every clone of sbase I make, and I imagine most other
> >> people want this as well. It is annoying to have `git status` scroll
> >> my changes off the screen due to all the build artifacts.
> >
> > Well, personnaly I don't want it, I prefer to have a clear view of the
> > clone status, hence the “user-side feature”, as in user-specific
> > preference.
>
> How do you deal with ~250 lines of "Untracked files:" in the `git
> status` output?
>
> If you want to see them, you can always run `git status --ignored`.

If you want it, you can always run `make .gitignore` *once*.

> >> The place for user-specific and repository-specific ignored files is
> >> .git/info/exclude. But in general, we don't know the location of the
> >> .git directory, so we'd probably have to use some git command to
> >> figure out exactly where to put it.
> >
> > There's no “we”, that's the user's responsability to figure out where
> > to put it.
>
> There is a "we" if a Makefile rule were to be added, since it needs to
> create the file at the appropriate location.

The appropriate location is .gitignore.
>
> > What's the rationale for having it duplicated both in the SCM and in the
> > Makefile then?
>
> So that if a utility is added or removed, .gitignore can easily be kept in sync.

So what's the point of having .gitignore tracked by the SCM?
Received on Mon Jun 17 2019 - 22:44:51 CEST