all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
Subject: Re: master 2644353: * .gitignore: add src/fingerprint.c
Date: Sat, 16 Jan 2021 15:55:54 -0800	[thread overview]
Message-ID: <86im7wcu7p.fsf@stephe-leake.org> (raw)
In-Reply-To: <jwv35z1rgds.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 15 Jan 2021 17:23:16 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> branch: master
>>> commit 2644353cbc65927a6a0a76d68e00d017771cdd03
>>
>>>     * .gitignore: add src/fingerprint.c
>>
>> Why? It's not generated since 2019-04-09.
>> Ref b697bb91a1
>
> BTW, this is a recurring problem: every time we change our build
> procedure such that an intermediate file isn't built any more,
> someone ends up (re)adding it to `.gitignore`.

Ah; I had fingerprint.c left over from some previous build, and did not
check that it is still generated.

I'll try to remember to check that in the future.

And to remember that other people keep .gitignore up to date, so a
previously generated file showing up means I should just delete it.

-- 
-- Stephe



  reply	other threads:[~2021-01-16 23:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210115180318.2341.87079@vcs0.savannah.gnu.org>
     [not found] ` <20210115180320.0E5AF20B2C@vcs0.savannah.gnu.org>
2021-01-15 21:38   ` master 2644353: * .gitignore: add src/fingerprint.c Glenn Morris
2021-01-15 22:23     ` Stefan Monnier
2021-01-16 23:55       ` Stephen Leake [this message]
2021-01-17  4:47         ` Stefan Monnier
2021-01-17 13:43           ` Basil L. Contovounesios
2021-01-17 13:56           ` Robin Tarsiger

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=86im7wcu7p.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@gnu.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.