all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robin Tarsiger <rtt@dasyatidae.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
	Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 2644353: * .gitignore: add src/fingerprint.c
Date: Sun, 17 Jan 2021 07:56:19 -0600	[thread overview]
Message-ID: <524d38be-9c44-7e72-25db-09f843cf4da1@dasyatidae.com> (raw)
In-Reply-To: <jwvft30kw6f.fsf-monnier+emacs@gnu.org>

Stefan Monnier wrote:
> I don't think it'll help: I made the same mistake in the past as have
> several others, then we learned, now you're learning as well but next
> time around there'll be inevitably someone else who hasn't learned
> it yet.

I would suggest that when a file transitions from generated to
source, it gains a negated entry in a section at the end of .gitignore
which is commented to this effect. That way, someone editing the file
at the end will see the negation section and be reminded to
slow down and check it, and someone editing an earlier section will
find that the effect is canceled out and be encouraged to pause and
look around for why.

(These can be pruned after some time if the section becomes large,
of course.)

-RTT



      parent reply	other threads:[~2021-01-17 13:56 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
2021-01-17  4:47         ` Stefan Monnier
2021-01-17 13:43           ` Basil L. Contovounesios
2021-01-17 13:56           ` Robin Tarsiger [this message]

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=524d38be-9c44-7e72-25db-09f843cf4da1@dasyatidae.com \
    --to=rtt@dasyatidae.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stephen_leake@stephe-leake.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.