From: Laurent Vivier <laurent@vivier.eu>
To: "Wang, Lei" <lei4.wang@intel.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, alex.bennee@linaro.org, f4bug@amsat.org
Subject: Re: [PATCH] .gitignore: add multiple items to .gitignore
Date: Sat, 22 Oct 2022 22:48:38 +0200 [thread overview]
Message-ID: <2c44912b-6e82-61b5-65f3-c2fe9d5664aa@vivier.eu> (raw)
In-Reply-To: <20221020171921.1078533-1-lei4.wang@intel.com>
Le 20/10/2022 à 19:19, Wang, Lei a écrit :
> Add /.vscode/, .clang-format and .gdb_history to .gitignore because:
>
> - For VSCode, workspace settings as well as debugging and task
> configurations are stored at the root in a .vscode folder;
> - For ClangFormat, the .clang-format file is searched relative to
> the current working directory when reading stdin;
> - For GDB, GDB command history file defaults to the value of the
> environment variable GDBHISTFILE, or to ./.gdb_history if this
> variable is not set.
>
> Signed-off-by: Wang, Lei <lei4.wang@intel.com>
> ---
> .gitignore | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/.gitignore b/.gitignore
> index 8aab671265..61fa39967b 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -1,10 +1,13 @@
> /GNUmakefile
> /build/
> /.cache/
> +/.vscode/
> *.pyc
> .sdk
> .stgit-*
> .git-submodule-status
> +.clang-format
> +.gdb_history
> cscope.*
> tags
> TAGS
Applied to my trivial-patches branch.
Thanks,
Laurent
prev parent reply other threads:[~2022-10-24 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 17:19 [PATCH] .gitignore: add multiple items to .gitignore Wang, Lei
2022-10-20 10:02 ` Philippe Mathieu-Daudé
2022-10-22 20:48 ` Laurent Vivier [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=2c44912b-6e82-61b5-65f3-c2fe9d5664aa@vivier.eu \
--to=laurent@vivier.eu \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=lei4.wang@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).