From: Michal Marek <mmarek@suse.cz>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: Jiri Kosina <trivial@kernel.org>,
Namhyung Kim <namhyung@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] .gitignore: Ingore rejected patch results
Date: Thu, 26 Apr 2012 10:31:28 +0200 [thread overview]
Message-ID: <4F9907E0.6010102@suse.cz> (raw)
In-Reply-To: <4F9906C0.3030109@suse.cz>
On 26.4.2012 10:26, Michal Marek wrote:
> On 26.4.2012 08:43, Namhyung Kim wrote:
>> Let git ignores *.rej files created when patch failed.
>
> I am not sure this is a good idea. If a patch fails and I have .rej
> files around, I really want to know about them.
And BTW, *.rej was added in commit 3f1b0e1 and removed one year later by
commit 1f5d3a6. So let's not switch it again.
Michal
prev parent reply other threads:[~2012-04-26 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 6:43 [PATCH] .gitignore: Ingore rejected patch results Namhyung Kim
2012-04-26 8:26 ` Michal Marek
2012-04-26 8:31 ` Michal Marek [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=4F9907E0.6010102@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@gmail.com \
--cc=sam@ravnborg.org \
--cc=trivial@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