From: Duy Nguyen <pclouds@gmail.com>
To: Sebastian Gniazdowski <psprint@zdharma.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: There should be a `.gitbless; file, protecting files from git clean
Date: Tue, 29 Jan 2019 07:48:45 +0700 [thread overview]
Message-ID: <CACsJy8Br9+m0pcErXDSsAMhhFd1xd8X0LfvLJvy63P45TX-zGQ@mail.gmail.com> (raw)
In-Reply-To: <etPan.5c4e9217.46ea0041.4d5@zdharma.org>
On Mon, Jan 28, 2019 at 12:24 PM Sebastian Gniazdowski
<psprint@zdharma.org> wrote:
>
> 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
next prev parent reply other threads:[~2019-01-29 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 2:41 There should be a `.gitbless; file, protecting files from git clean Sebastian Gniazdowski
2019-01-28 5:05 ` Duy Nguyen
2019-01-28 5:24 ` Sebastian Gniazdowski
2019-01-29 0:48 ` Duy Nguyen [this message]
2019-01-28 6:23 ` Sebastian Gniazdowski
2019-01-28 15:30 ` Sebastian Gniazdowski
2019-01-29 1:00 ` Duy Nguyen
2019-01-28 18:08 ` Junio C Hamano
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=CACsJy8Br9+m0pcErXDSsAMhhFd1xd8X0LfvLJvy63P45TX-zGQ@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=psprint@zdharma.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.
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).