From: David Lang <david@lang.hm>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Is there a way to have a local version of a header file?
Date: Sat, 18 Mar 2017 15:40:08 -0700 (PDT) [thread overview]
Message-ID: <nycvar.QRO.7.75.62.1703181539310.3797@qynat-yncgbc> (raw)
In-Reply-To: <xmqqzigi31fl.fsf@gitster.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
On Sat, 18 Mar 2017, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> There might be some way I haven't thought of, in particular maybe you
>> can use gitattributes to define a custom diff/merge driver that always
>> reports no changes, or some ways to (ab)use the index to make git
>> ignore any changes to the file.
>
> Why does this have to be so difficult?
>
> Ship a config.h.sample file, have a Makefile rule that is forced to
> run before any compilation happens that checks if config.h exists
> and then created it if missing by copying config.h.sample over, and
> then all other source files can include config.h without having to
> know anything about config.h.sample's existence.
>
> Did I miss something?
There is no makefile with the arduino IDE/build system :-(
David Lang
next prev parent reply other threads:[~2017-03-18 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 14:29 Is there a way to have a local version of a header file? David Lang
2017-03-18 14:48 ` Ævar Arnfjörð Bjarmason
2017-03-18 14:58 ` David Lang
2017-03-18 17:08 ` Ævar Arnfjörð Bjarmason
2017-03-18 18:05 ` Junio C Hamano
2017-03-18 22:40 ` David Lang [this message]
2017-03-18 23:11 ` Junio C Hamano
2017-03-18 23:22 ` Samuel Lijin
2017-03-19 21:33 ` Johannes Sixt
2017-03-19 0:19 ` David Lang
2017-03-18 18:21 ` Jakub Narębski
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=nycvar.QRO.7.75.62.1703181539310.3797@qynat-yncgbc \
--to=david@lang.hm \
--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).