Re: There should be a `.gitbless; file, protecting files from git clean

From: Duy Nguyen <pclouds@gmail.com>
Date: Jan 29, 2019, 00:48 UTC
Message-ID: <CACsJy8Br9+m0pcErXDSsAMhhFd1xd8X0LfvLJvy63P45TX-zGQ@mail.gmail.com>
In-Reply-To: <etPan.5c4e9217.46ea0041.4d5@zdharma.org>

On Mon, Jan 28, 2019 at 12:24 PM Sebastian Gniazdowski <psprint@zdharma.org> wrote:

Show 17 quoted lines

>
> On 28 stycznia 2019 at 06:05:31, Duy Nguyen (pclouds@gmail.com) wrote:
> > On Mon, Jan 28, 2019 at 9:54 AM Sebastian Gniazdowski
> > wrote:
> > >
> > > Hello,
> > > Could a .gitbless file be a solution? I would list in it, e.g.:
> > >
> > > TODO
> > >
> > > and this way be able to use `git -dxf' again. What do you think?
> >
> > There's a patch that adds "precious" git attribute [1]. I was going to
> > resend once the backup-log [2] got reviewed but I might just send it
> > separately to handle the "git clean" case alone.
>
> That would be nice solution. In the email, you ask for a name other than "precious". So maybe "blessed"?

There's a couple mail replies in that thread that pointed out "precious" has been used elsewhere (I think Makefile is one) so I think I'm going to stick with "precious". Besides it sounds "precious" :D

-- 
Duy