From: Bodo Eggert <7eggert@gmx.de>
To: Ingo Molnar <mingo@elte.hu>,
jeremy@goop.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, sam@ravnborg.org,
gitster@pobox.com, caglar@pardus.org.tr,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] Add *.rej to .gitignore
Date: Thu, 19 Feb 2009 21:25:28 +0100 [thread overview]
Message-ID: <E1LaFSb-0002J5-6Z@be1.7eggert.dyndns.org> (raw)
In-Reply-To: <c6IaO-60k-5@gated-at.bofh.it>
Ingo Molnar <mingo@elte.hu> wrote:
> * David Miller <davem@davemloft.net> wrote:
>> From: Jeremy Fitzhardinge <jeremy@goop.org>
>> > *.rej files really are unwanted. If there are any .rej files, they can be
>> > found by some other means (perhaps git itself could warn when committing
>> > with *.rej files present, or add some distinct notion of "ignored files" vs
>> > "never commit" files).
>> >
>> > (This effectively reverts 1f5d3a6b6532e25a5cdf1f311956b2b03d343a48)
>> >
>> > Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>>
>> I don't know about this.
>>
>> I really want to know if there are reject files there if I am
>> checking to see if my tree is clean.
[...]
> Well, it depends on the workflow. You are making the assumption
> that everyone is using your workflow, and you are judging them
> based on that false assumption.
If different users need different .gitignores, you need a per-user setting.
Let there be ~/.git/gitignore.
next parent reply other threads:[~2009-02-19 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c6Eh1-7Og-19@gated-at.bofh.it>
[not found] ` <c6GLO-3xO-35@gated-at.bofh.it>
[not found] ` <c6IaO-60k-5@gated-at.bofh.it>
2009-02-19 20:25 ` Bodo Eggert [this message]
2009-02-17 19:59 Jeremy Fitzhardinge
2009-02-17 20:08 ` Sam Ravnborg
2009-02-17 21:16 ` Linus Torvalds
2009-02-17 21:36 ` Ingo Molnar
2009-02-17 22:20 ` Alexey Dobriyan
2009-02-17 22:38 ` David Miller
2009-02-18 0:05 ` Ingo Molnar
2009-02-18 0:40 ` Sam Ravnborg
2009-02-18 0:49 ` Ingo Molnar
2009-02-18 1:05 ` David Miller
2009-02-18 15:21 ` Stefan Richter
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=E1LaFSb-0002J5-6Z@be1.7eggert.dyndns.org \
--to=7eggert@gmx.de \
--cc=caglar@pardus.org.tr \
--cc=davem@davemloft.net \
--cc=gitster@pobox.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®