From: Philip Oakley <philipoakley@iee.email>
To: "без имени" <mykaralw@yandex.ru>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: .git/binary
Date: Fri, 25 Oct 2019 21:59:24 +0100 [thread overview]
Message-ID: <5f558e34-bdb2-6656-d2ca-42a2d7cb8874@iee.email> (raw)
In-Reply-To: <24796381572021130@iva7-56e9317134d0.qloud-c.yandex.net>
On 25/10/2019 17:32, без имени wrote:
>> Or were you thinking of some other meaning for "files stored in a single (current) state"?
> It means that new versions of files located in `.git / binary` will completely replace old versions in history, and therefore will be in a single (current) state in history. What used to be another version of this file should be ignored (very useful for PNG, JPEG, PDF).
>
"completely replace old versions in history" : but why?
- Is it a space (size on disc, or memory) problem/limitation
- A confidentiality problem?
- A 'must use latest procedure' (always checkout latest instructions)
problem?
- A synchronisation problem (no adequate diff) needing single line of
development? (there was a discussion at Git Merge in February about this
for modified Audio-Visual (AV) files in Games development
“Git for games: current problems and solutions” presentation by John
Austin at Git Merge 2019:
https://www.youtube.com/watch?v=K3zOhU3NdWA&list=PL0lo9MOBetEFqBue4vNcTEnkBjgIQU1Q3&index=8&t=0s
- Something else?
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
--
Philip
next prev parent reply other threads:[~2019-10-25 20:59 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 ` Philip Oakley [this message]
2019-10-25 21:33 ` .git/binary без имени
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=5f558e34-bdb2-6656-d2ca-42a2d7cb8874@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=mykaralw@yandex.ru \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.