public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH 1/2] Split top level .gitignore file
Date: Sun, 20 Dec 2020 16:28:30 +0100	[thread overview]
Message-ID: <20201220152830.GA54564@wildebeest.org> (raw)
In-Reply-To: <20201220121119.GA26424@altlinux.org>

Hi Dmitry,

On Sun, Dec 20, 2020 at 03:11:19PM +0300, Dmitry V. Levin wrote:
> Move subdirectory parts of the top level .gitignore into appropriate
> subdirectories.  This would be consistent with ChangeLog files,
> currently one has to update the top level ChangeLog file when the top
> level .gitignore file is changed in a way that affects specific
> subdirectories only.

Both changes look good to me. The only thing I would double check is
the /*.map entry in backends/.gitignore. It obviously comes from the
top-level .gitignore. But I don't know why it was there in the first
place.

Thanks,

Mark

  reply	other threads:[~2020-12-20 15:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 23:40 [PATCH] Modernize gettext infrastructure Dmitry V. Levin
2020-12-15 23:46 ` Q: splitting the top level .gitignore file Dmitry V. Levin
2020-12-16 13:44   ` Mark Wielaard
2020-12-20 12:11     ` [PATCH 1/2] Split " Dmitry V. Levin
2020-12-20 15:28       ` Mark Wielaard [this message]
2020-12-20 15:37         ` Dmitry V. Levin
2020-12-20 15:59           ` Dmitry V. Levin
2020-12-20 16:09             ` Mark Wielaard
2020-12-20 12:11     ` [PATCH 2/2] Update .gitignore files Dmitry V. Levin
2020-12-16 14:05 ` [PATCH] Modernize gettext infrastructure Mark Wielaard
2020-12-16 14:59   ` Dmitry V. Levin
2020-12-16 15:10     ` Mark Wielaard

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=20201220152830.GA54564@wildebeest.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=ldv@altlinux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).