Re: [PATCH v3 3/4] doc: dissuade users from trying to ignore tracked files
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Nov 4, 2019, 23:52 UTC
- Message-ID
- <20191104235242.GD32531@camp.crustytoothpaste.net>
- In-Reply-To
- <20191104222416.GB22367@sigill.intra.peff.net>
On 2019-11-04 at 22:24:16, Jeff King wrote:
Show 25 quoted lines
> On Sun, Nov 03, 2019 at 06:59:08PM +0000, brian m. carlson wrote: > > > > I would really like to see a simple example of such template, so that > > > even people who are unfamiliar with Ruby's ERB can think of equivalent > > > solution for their language or toolchain of choice. > > > > I hesitated to mention ERB, but I wasn't sure that folks would know what > > we meant by a "templating mechanism". The reason I had chosen to > > mention it is that someone could search for "Ruby ERB" and find out what > > it looked like and then look for an option in their own language. > > I don't mind what is here, but I might even suggest going slightly in > the opposite direction. Say something like: > > For example, you the repository can include a sample config file that > can then be copied into the ignored name and modified. > > which points people in the right direction without giving specifics. But > if you did want to go further, you can then say: > > The repository can even include a script to treat the sample file as a > template, modifying and copying it automatically (e.g., a Ruby script > using an ERB template). > > or something.
I think this is a nice change. It summarizes the proposed solution without needing to be specific.
-- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204