From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
jbeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] gitignore: Don't ignore *.rej
Date: Thu, 13 Aug 2015 11:32:09 +0100 [thread overview]
Message-ID: <1439461929.23981.71.camel@citrix.com> (raw)
In-Reply-To: <21963.25751.496570.780266@mariner.uk.xensource.com>
On Wed, 2015-08-12 at 16:21 +0100, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [PATCH] gitignore: Don't
> ignore *.rej"):
> > On Wed, Aug 12, 2015 at 10:07:37AM +0100, Ian Campbell wrote:
> > > These indicate a patch application went wrong, I want to see them in
> > > "git status". This appears to have been imported from .hgignore where
> > > it has been since 2005.
> > >
> > > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > > Cc: Daniel Kiper <daniel.kiper@oracle.com>
> >
> > Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>
> (As an aside, I would normally apply a `usual' kind of trivial
> .gitignore update without waiting for any kind of ack. But this one
> seems not entirely trivial.)
Right, I thought it might even be controversial, but it seems not. I've
applied.
next prev parent reply other threads:[~2015-08-13 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:07 [PATCH] gitignore: Don't ignore *.rej Ian Campbell
2015-08-12 9:19 ` Jan Beulich
2015-08-12 14:31 ` Konrad Rzeszutek Wilk
2015-08-12 15:21 ` Ian Jackson
2015-08-13 10:32 ` Ian Campbell [this message]
2015-08-12 18:09 ` Daniel Kiper
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=1439461929.23981.71.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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 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.