From: Junio C Hamano <gitster@pobox•com>
To: Duy Nguyen <pclouds@gmail•com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail•com>,
"Git Mailing List" <git@vger•kernel.org>,
"Per Lundberg" <per.lundberg@hibox•tv>,
"Steffen Jost" <jost@tcs•ifi.lmu.de>,
"Joshua Jensen" <jjensen@workspacewhiz•com>,
"Matthieu Moy" <git@matthieu-moy•fr>,
"Clemens Buchacher" <drizzd@gmx•net>,
"Holger Hellmuth" <hellmuth@ira•uka.de>,
"Kevin Ballard" <kevin@sb•org>
Subject: Re: [PATCH 1/1] Introduce "precious" file concept
Date: Tue, 19 Feb 2019 10:08:16 -0800 [thread overview]
Message-ID: <xmqq8syb3b3j.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACsJy8CR7VGp7htC_wKC9BUCaQsmkp5Zd4+M7bddPL-jKyfDMQ@mail.gmail.com> (Duy Nguyen's message of "Sun, 17 Feb 2019 16:31:56 +0700")
Duy Nguyen <pclouds@gmail•com> writes:
> On Sun, Feb 17, 2019 at 2:36 AM Ævar Arnfjörð Bjarmason
> <avarab@gmail•com> wrote:
>>
>>
>> On Sat, Feb 16 2019, Nguyễn Thái Ngọc Duy wrote:
>>
>> [Re-CC some people involved the last time around]
>>
>> > A new attribute "precious" is added to indicate that certain files
>> > have valuable content and should not be easily discarded even if they
>> > are ignored or untracked.
>> >
>> > So far there are one part of Git that are made aware of precious
>> > files: "git clean" will leave precious files alone.
>>
>> Thanks for bringing this up again. There were also some patches recently
>> to save away clobbered files, do you/anyone else have any end goal in
>> mind here that combines this & that, or some other thing I may not have
>> kept up with?
>
> I assume you mean the clobbering untracked files by merge/checkout.
> Those files will be backed up [1] if backup-log is implemented. Even
> files deleted by "git clean" could be saved but that might go a little
> too far.
I agree with Ævar that it is a very good idea to ask what the
endgame should look like. I would have expected that, with an
introduction of new "ignored but unexpendable" class of file
(i.e. "precious" here), operations such as merge and checkout will
be updated to keep them in situations where we would remove "ignored
and expendable" files (i.e. "ignored"). And it is perfectly OK if
the very first introduction of the "precious" support begins only
with a single operation, such as "clean", as long as the end-goal is
clear.
I personally do not believe in "backup log"; if we can screw up and
can fail to stop an operation that must avoid losing info, then we
can screw up the same way and fail to design and implement "backup"
to save info before an operation loses it. If we do a good job in
supporting "precious" in various operations, we can rely less on
"backup log" and still be safe ;-)
next prev parent reply other threads:[~2019-02-19 18:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 11:49 [PATCH 0/1] Introduce "precious" file attribute Nguyễn Thái Ngọc Duy
2019-02-16 11:49 ` [PATCH 1/1] Introduce "precious" file concept Nguyễn Thái Ngọc Duy
2019-02-16 19:36 ` Ævar Arnfjörð Bjarmason
2019-02-17 9:31 ` Duy Nguyen
2019-02-18 9:53 ` Ævar Arnfjörð Bjarmason
2019-02-18 10:14 ` Duy Nguyen
2019-02-19 18:08 ` Junio C Hamano [this message]
2019-02-20 1:35 ` Duy Nguyen
2019-02-20 8:31 ` Clemens Buchacher
2019-02-20 22:32 ` Junio C Hamano
2019-02-20 9:19 ` Ævar Arnfjörð Bjarmason
2019-02-20 9:36 ` Steffen Jost
2019-02-20 9:41 ` Duy Nguyen
2019-02-20 10:46 ` Ævar Arnfjörð Bjarmason
2019-02-20 11:11 ` Clemens Buchacher
2019-02-22 9:46 ` Duy Nguyen
2019-02-20 22:39 ` Junio C Hamano
2019-02-22 9:35 ` Duy Nguyen
2019-02-22 18:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8syb3b3j.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox$(echo .)com \
--cc=avarab@gmail$(echo .)com \
--cc=drizzd@gmx$(echo .)net \
--cc=git@matthieu-moy$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=hellmuth@ira$(echo .)uka.de \
--cc=jjensen@workspacewhiz$(echo .)com \
--cc=jost@tcs$(echo .)ifi.lmu.de \
--cc=kevin@sb$(echo .)org \
--cc=pclouds@gmail$(echo .)com \
--cc=per.lundberg@hibox$(echo .)tv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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