public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: [PATCH 1/8] debian: Add all temporary files to Gitignore
Date: Mon, 19 Apr 2021 14:10:55 +0100	[thread overview]
Message-ID: <85231BA2-81AD-4E34-AD4E-427D267FE6E2@ipfire.org> (raw)
In-Reply-To: <20210416130612.15959-2-valter.jansons@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]

Hello,

> On 16 Apr 2021, at 14:06, Valters Jansons <valter.jansons(a)gmail.com> wrote:
> 
> New packages have been added since the inception of the .gitignore and
> as a result during build we see directories such as location-importer/
> and files such as location-importer.debhelper.log.
> 
> This commit ensures all temporary subdirectories, and additional
> generic build artifact files, are ignored by Git.
> 
> The subdirectory exceptions to this rule are:
> 
> - d/patches/ which may be used by Quilt
>  considering the source format is '3.0 (quilt)',
> 
> - d/source/ for the format file,
> 
> - d/tests/ which may be used by autopkgtest
>  to specify what test suites exist for the source.
>  See: https://salsa.debian.org/ci-team/autopkgtest/-/raw/debian/5.16/doc/README.package-tests.rst
> 
> Signed-off-by: Valters Jansons <valter.jansons(a)gmail.com>
> ---
> debian/.gitignore | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/debian/.gitignore b/debian/.gitignore
> index 0faf920..8190b92 100644
> --- a/debian/.gitignore
> +++ b/debian/.gitignore
> @@ -2,9 +2,10 @@
> /autoreconf.*
> /debhelper-build-stamp
> /files
> -/libloc/
> -/libloc-dev/
> -/libloc-perl/
> -/tmp
> +/*/

What is /*/ for? Why would we ignore any directory that is created in the root directory.

It feels like a bit much to me.

-Michael

> *.debhelper
> +*.log
> *.substvars
> +!/patches/
> +!/source/
> +!/tests/
> -- 
> 2.31.1
> 


  reply	other threads:[~2021-04-19 13:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 13:06 [PATCH 0/8] debian: Mitigate bulk of Lintian issues Valters Jansons
2021-04-16 13:06 ` [PATCH 1/8] debian: Add all temporary files to Gitignore Valters Jansons
2021-04-19 13:10   ` Michael Tremer [this message]
2021-04-19 13:48     ` Valters Jansons
2021-04-16 13:06 ` [PATCH 2/8] debian: Move libloc1 to 'libs' section Valters Jansons
2021-04-16 13:06 ` [PATCH 3/8] debian: Set 'Multi-Arch: foreign' hint for Python Valters Jansons
2021-04-16 13:06 ` [PATCH 4/8] debian: Update copyright format link to use HTTPS Valters Jansons
2021-04-16 13:06 ` [PATCH 5/8] debian: Add examples/python/ to documentation Valters Jansons
2021-04-16 13:06 ` [PATCH 6/8] debian: Drop unintended files from location-python Valters Jansons
2021-04-19 13:14   ` Michael Tremer
2021-04-19 13:56     ` Valters Jansons
2021-04-16 13:06 ` [PATCH 7/8] debian: Add watch configuration for uscan Valters Jansons
2021-04-19 13:15   ` Michael Tremer
2021-04-16 13:06 ` [PATCH 8/8] systemd: Add Documentation= to location-update Valters Jansons
2021-04-19 13:10 ` [PATCH 0/8] debian: Mitigate bulk of Lintian issues Michael Tremer
2021-04-27  9:28   ` Valters Jansons
2021-05-04 14:50     ` Michael Tremer
2021-05-04 18:40       ` Valters Jansons
2021-05-06 15:12         ` Michael Tremer
2021-05-06 17:37           ` Valters Jansons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85231BA2-81AD-4E34-AD4E-427D267FE6E2@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=location@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox