git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: git@vger.kernel.org
Subject: Is there a way to have a local version of a header file?
Date: Sat, 18 Mar 2017 07:29:50 -0700 (PDT)	[thread overview]
Message-ID: <nycvar.QRO.7.75.62.1703180724490.3797@qynat-yncgbc> (raw)

for an embedded project built inside the Arduino IDE, (alternate firmware for a 
home automation project) there is a need to set a number of parameters that we 
really don't want in the main repo (wifi network IDs/passwords)

right now, we have these things set as #defines in a header file.

We need to distribute a base version of this file for new people to get started.

Is there any way to have git define a file in such a way that if it doesn't 
exist in the worktree it gets populated, but if it does exist it doesn't get 
overwritten? (as I type this, I'm thinking a trigger may work, but we need it to 
work on Linux, Windows and OSX)

Any thoughts on a sane way to handle this situation?

David Lang

             reply	other threads:[~2017-03-18 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 14:29 David Lang [this message]
2017-03-18 14:48 ` Is there a way to have a local version of a header file? Æ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
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

* 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.1703180724490.3797@qynat-yncgbc \
    --to=david@lang.hm \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).