From: "без имени" <mykaralw@yandex.ru>
To: Philip Oakley <philipoakley@iee.email>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: .git/binary
Date: Sat, 26 Oct 2019 00:33:19 +0300 [thread overview]
Message-ID: <25196441572039199@iva5-58d151f416d2.qloud-c.yandex.net> (raw)
In-Reply-To: <5f558e34-bdb2-6656-d2ca-42a2d7cb8874@iee.email>
> The main advantage of Git is that it distributes control from some central 'manager' to the individual and does that by taking snapshots and exchanging verification stamps, so the idea of deleting history feels somehow 'wrong', hence the need to understand
I perfectly understand that by removing information about the file and its changes from the history, I will “delete” it completely. Git needs changes to work. That means you will need an additional utility file, for example, `.gitshadow`, containing the sum of the files in the list. And this service file will already be reflected in the history. Moreover, it must be to process in a special way.
What is this "all" for?
Too much that is in `git` is completely useless to anyone. This mechanism (if it is implemented) will not be needed by everyone, but those who need it will be very gracious for freeing useless the mountains of trash.
--
zvezdochiot
prev parent reply other threads:[~2019-10-25 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 8:53 .git/binary без имени
2019-10-25 15:10 ` .git/binary Philip Oakley
2019-10-25 16:32 ` .git/binary без имени
2019-10-25 18:05 ` .git/binary Pratyush Yadav
2019-10-25 18:27 ` .git/binary без имени
2019-10-25 18:40 ` .git/binary без имени
2019-10-25 20:59 ` .git/binary Philip Oakley
2019-10-25 21:33 ` без имени [this message]
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=25196441572039199@iva5-58d151f416d2.qloud-c.yandex.net \
--to=mykaralw@yandex.ru \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.email \
/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).