From: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, Andreas Ericsson <ae@op5.se>,
git@vger.kernel.org
Subject: Re: [PATCH] .gitignore git-rerere and config.mak
Date: Wed, 08 Feb 2006 00:23:41 +0100 [thread overview]
Message-ID: <43E92BFD.7060909@gorzow.mm.pl> (raw)
In-Reply-To: <Pine.LNX.4.63.0602071951370.26070@wbgn013.biozentrum.uni-wuerzburg.de>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Johannes Schindelin wrote:
> Hi,
>
> On Tue, 7 Feb 2006, Junio C Hamano wrote:
>
>> Andreas Ericsson <ae@op5.se> writes:
>>
>>> --- a/.gitignore
>>> +++ b/.gitignore
>>> @@ -123,3 +124,4 @@ git-core.spec
>>> libgit.a
>>> *.o
>>> *.py[co]
>>> +config.mak
>> I am not sure about this part. It is plausible that somebody
>> who privately uses config.mak has it in _his_ repository under
>> version control. Should we list it in .gitignore?
>
> I have it in .gitignore. If there were changes to config.mak which I had
> in all my copies of git, I'd have them directly in the Makefile.
>
> Hth,
> Dscho
Somehow git-rerere didn't end up getting included in .gitignore...
--
GPG Key id: 0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0 9105 9543 0453 D1F1 0BA2
AstralStorm
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-02-08 0:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 17:23 [PATCH] .gitignore git-rerere and config.mak Andreas Ericsson
2006-02-07 18:20 ` Junio C Hamano
2006-02-07 18:52 ` Johannes Schindelin
2006-02-07 23:23 ` Radoslaw Szkodzinski [this message]
2006-02-08 1:01 ` Junio C Hamano
2006-02-08 3:55 ` Jason Riedy
2006-02-08 5:34 ` Junio C Hamano
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=43E92BFD.7060909@gorzow.mm.pl \
--to=astralstorm@gorzow.mm.pl \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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