From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Add git format-patch produced patches to .gitignore
Date: Sun, 16 May 2010 16:05:41 +0200 [thread overview]
Message-ID: <4BEFFBB5.7010808@drmicha.warpmail.net> (raw)
In-Reply-To: <1273958566-7328-1-git-send-email-avarab@gmail.com>
Ævar Arnfjörð Bjarmason venit, vidit, dixit 15.05.2010 23:22:
> Change Git's own .gitignore so that patches produced with git
> format-patch don't show up as untracked.
>
Does the git build process call format-patch? No! The .gitignore we
distribute is meant for things the build process creates, not for
imposing a specific workflow on developers.
If you want to ignore format patch output, simply use .git/info/excludes
or a global excludes file, but please don't force everyone else to live
with that or work around it.
Cheers,
Michael
> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> ---
> .gitignore | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/.gitignore b/.gitignore
> index dbf1b90..039d99c 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -203,3 +203,4 @@
> *.pdb
> /Debug/
> /Release/
> +[0-9][0-9][0-9][0-9]-*.patch
next prev parent reply other threads:[~2010-05-16 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 21:22 [PATCH] Add git format-patch produced patches to .gitignore Ævar Arnfjörð Bjarmason
2010-05-16 6:27 ` Pavan Kumar Sunkara
2010-05-16 7:52 ` Jonathan Nieder
2010-05-16 13:06 ` Ævar Arnfjörð Bjarmason
2010-05-16 14:05 ` Michael J Gruber [this message]
2010-05-17 1:35 ` Jonathan Nieder
2010-05-17 2:04 ` [PATCH] Remove editor-specific droppings from .gitignore Ævar Arnfjörð Bjarmason
2010-05-17 2:22 ` [PATCH] Add git format-patch produced patches to .gitignore Jonathan Nieder
2010-05-17 7:52 ` Michael J Gruber
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BEFFBB5.7010808@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).