From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Íñigo Huguet" <ihuguet@redhat.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Alexey Dobriyan" <adobriyan@sw.ru>,
"S.Çağlar Onur" <caglar@pardus.org.tr>
Subject: Re: [PATCH] Remove *.orig pattern from .gitignore
Date: Sat, 17 Aug 2024 22:33:42 +0300 [thread overview]
Message-ID: <20240817193342.GA12234@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20240801011120.GA1620143@thelio-3990X>
On Wed, Jul 31, 2024 at 06:11:20PM -0700, Nathan Chancellor wrote:
> On Mon, Jul 29, 2024 at 06:57:38PM +0300, Laurent Pinchart wrote:
> > Commit 3f1b0e1f2875 (".gitignore update") added *.orig and *.rej
> > patterns to .gitignore in v2.6.23. The commit message didn't give a
> > rationale. Later on, commit 1f5d3a6b6532 ("Remove *.rej pattern from
> > .gitignore") removed the *.rej pattern in v2.6.26, on the rationale that
> > *.rej files indicated something went really wrong and should not be
> > ignored.
> >
> > The *.rej files are now shown by `git status`, which helps located
> > conflicts when applying patches and lowers the probability that they
> > will go unnoticed. It is however still easy to overlook the *.orig files
> > which slowly polute the source tree. That's not as big of a deal as not
> > noticing a conflict, but it's still not nice.
> >
> > Drop the *.orig pattern from .gitignore to avoid this and help keep the
> > source tree clean.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> > As this has been in the tree for so long and appears not to have botherd
> > anyone, I have a strong feeling I've overlooked something and this patch
> > will be rejected. I've actually had that feeling for a few years
> > already, and today I decided that maybe everybody else used the exact
> > same reasoning, explaining why the annoying *.orig pattern is still in
> > .gitignore.
>
> I don't really have a strong opinion myself but it does seem reasonable
> to be consistent. For what it's worth, Stephen Rothwell checks for
> accidentally added .orig and .rej files in -next (and catches them
> occasionally [1]), so I wouldn't expect removing this to matter much.
>
> [1]: https://lore.kernel.org/linux-next/?q=.rej
I didn't know that, it's useful information, thanks. I wonder if
checkpatch.pl could also check for that ? Although git-add already
warns unless you specify -f, so people ignoring that may also ignore
checkpatch.pl, I'm not sure.
Who decides on whether this patch should be merged ?
> > ---
> > .gitignore | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/.gitignore b/.gitignore
> > index 7902adf4f7f1..58fdbb35e2f1 100644
> > --- a/.gitignore
> > +++ b/.gitignore
> > @@ -142,7 +142,6 @@ GTAGS
> > # id-utils files
> > ID
> >
> > -*.orig
> > *~
> > \#*#
> >
> >
> > base-commit: 8400291e289ee6b2bf9779ff1c83a291501f017b
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-08-17 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 15:57 [PATCH] Remove *.orig pattern from .gitignore Laurent Pinchart
2024-08-01 1:11 ` Nathan Chancellor
2024-08-17 19:33 ` Laurent Pinchart [this message]
2024-08-17 19:49 ` Laurent Pinchart
2024-08-18 12:20 ` Masahiro Yamada
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=20240817193342.GA12234@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=adobriyan@sw.ru \
--cc=caglar@pardus.org.tr \
--cc=ihuguet@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=masahiroy@kernel.org \
--cc=mic@digikod.net \
--cc=nathan@kernel.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 NNTP newsgroup(s).