xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Add .gitignore files for files generated by the hypervisor build
Date: Tue, 10 Jan 2012 18:36:36 +0000	[thread overview]
Message-ID: <CB3235B4.287E2%keir.xen@gmail.com> (raw)
In-Reply-To: <20236.30074.784658.148457@mariner.uk.xensource.com>

On 10/01/2012 17:29, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> David Vrabel writes ("[Xen-devel] [PATCH] Add .gitignore files for files
> generated by the hypervisor build"):
>> More or fewer .gitignore files could be used.  Let me know which is
>> preferred.
> 
> I have a branch containing a complete .gitignore for the whole tree.
> 
> I would have absolutely no objection to submitting it.  Would anyone
> object to it going into tree ?

I'm sure we've done both .hgignore/.gitignore in some repositories in the
past. It sounds fine to me.

 -- Keir

> Obviously we will still expect patches to come with any necessary
> .hgignore updates and not necessarily updates to .gitignore.  I would
> be happy to be maintainer for the .gitignore (since I'm doing that
> work anyway...)
> 
> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2012-01-10 18:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 15:54 [PATCH] Add .gitignore files for files generated by the hypervisor build David Vrabel
2012-01-10 17:29 ` Ian Jackson
2012-01-10 18:36   ` Keir Fraser [this message]
2012-01-12 16:33     ` Ian Jackson
2012-01-12 16:40       ` Keir Fraser
2012-01-12 16:45         ` Ian Jackson

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=CB3235B4.287E2%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).