From: George Dunlap <george.dunlap@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2 1/3] gitignore: ignore .vscode directory
Date: Wed, 15 May 2019 12:38:54 +0100 [thread overview]
Message-ID: <a366b1f8-778c-c9f4-66cd-335cc92cc418@citrix.com> (raw)
In-Reply-To: <20190514142233.23165-2-wei.liu2@citrix.com>
On 5/14/19 3:22 PM, Wei Liu wrote:
> The directory is created by Visual Studio Code editor to store its
> local state.
>
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Acked-by: George Dunlap <george.dunlap@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: George Dunlap <george.dunlap@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [Xen-devel] [PATCH v2 1/3] gitignore: ignore .vscode directory
Date: Wed, 15 May 2019 12:38:54 +0100 [thread overview]
Message-ID: <a366b1f8-778c-c9f4-66cd-335cc92cc418@citrix.com> (raw)
Message-ID: <20190515113854.ayTmdzj4noDEqpr-dmNfw9SWJhF4-om3pkfGCHoqYMY@z> (raw)
In-Reply-To: <20190514142233.23165-2-wei.liu2@citrix.com>
On 5/14/19 3:22 PM, Wei Liu wrote:
> The directory is created by Visual Studio Code editor to store its
> local state.
>
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Acked-by: George Dunlap <george.dunlap@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-15 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 14:22 [PATCH v2 0/3] Misc patches Wei Liu
2019-05-14 14:22 ` [Xen-devel] " Wei Liu
2019-05-14 14:22 ` [PATCH v2 1/3] gitignore: ignore .vscode directory Wei Liu
2019-05-14 14:22 ` [Xen-devel] " Wei Liu
2019-05-15 11:38 ` George Dunlap [this message]
2019-05-15 11:38 ` George Dunlap
2019-05-14 14:22 ` [PATCH v2 2/3] README: document requirement about python Wei Liu
2019-05-14 14:22 ` [Xen-devel] " Wei Liu
2019-05-14 14:34 ` Jan Beulich
2019-05-14 14:34 ` [Xen-devel] " Jan Beulich
2019-05-14 14:22 ` [PATCH v2 3/3] INSTALL: remove duplicate sentence Wei Liu
2019-05-14 14:22 ` [Xen-devel] " Wei Liu
2019-05-15 11:40 ` George Dunlap
2019-05-15 11:40 ` [Xen-devel] " George Dunlap
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=a366b1f8-778c-c9f4-66cd-335cc92cc418@citrix.com \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).