From: Antony Male <antony.male@gmail.com>
To: Peter Lauri <peterlauri@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: .gitignore behavior on Mac
Date: Sun, 19 May 2013 11:54:36 +0100 [thread overview]
Message-ID: <5198AF6C.8080402@gmail.com> (raw)
In-Reply-To: <CAEe6bfC6F3sN_OXZYo1=bdwo01_7qFUEmbSWVFNaFZQrZUGdWA@mail.gmail.com>
On 18/05/2013 23:37, Peter Lauri wrote:
> Great, I have gotten the concept now :)
>
> My workaround for my problem is to rename the file to ....default and
> then all will work out well :) Copy the file then and locally modify
> it, but it will be in .gitignore so not tracked :)
Over in the #git IRC channel, we point users asking this question to
https://gist.github.com/canton7/1423106. It contains that approach, and
quite a few others.
Antony
prev parent reply other threads:[~2013-05-19 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 18:36 .gitignore behavior on Mac Peter Lauri
2013-05-18 18:41 ` John Keeping
2013-05-18 18:43 ` Peter Lauri
2013-05-18 18:55 ` John Keeping
2013-05-18 21:01 ` Johannes Sixt
2013-05-18 22:37 ` Peter Lauri
2013-05-19 7:47 ` Junio C Hamano
2013-05-19 10:54 ` Antony Male [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=5198AF6C.8080402@gmail.com \
--to=antony.male@gmail.com \
--cc=git@vger.kernel.org \
--cc=peterlauri@gmail.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.
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).