git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Samuel Lijin <sxlijin@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"David Lang" <david@lang.hm>,
	"Æ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: Sun, 19 Mar 2017 22:33:33 +0100	[thread overview]
Message-ID: <5d06ba31-bec1-0172-cb00-10b4d2c4e648@kdbg.org> (raw)
In-Reply-To: <CAJZjrdVxT7G+Cn+1_vqPBCtMOALmR_542jvP7nXXuvs74ko5qg@mail.gmail.com>

Am 19.03.2017 um 00:22 schrieb Samuel Lijin:
> I'd just provide a .sample and tell people what to do with it in the
> README. The alternative is to provide config.h as is and tell people
> to use "git update-index --assume-unchanged" immediately after cloning
> to ignore changes to the file, but this is prone to people
> accidentally committing credentials.

Please do not suggest to use --assume-unchanged. It is not intended for 
this purpose, and if used in the way you suggest, it will sooner or 
later bite back.

--assume-unchanged is a promise to Git that you do not change the file. 
If you break the promise, you get what you deserve ;)

-- Hannes


  reply	other threads:[~2017-03-19 21:33 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
2017-03-18 23:11           ` Junio C Hamano
2017-03-18 23:22             ` Samuel Lijin
2017-03-19 21:33               ` Johannes Sixt [this message]
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=5d06ba31-bec1-0172-cb00-10b4d2c4e648@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=avarab@gmail.com \
    --cc=david@lang.hm \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sxlijin@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. 
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).