Control: tags -1 pending
Hello Max,
Am 08.08.23 um 13:31 schrieb Max Nikulin:
On 05/08/2023 13:08, Carsten Schoenert wrote:
Could you please cut all these additions into own peaces/patches?
By this it's more visible what the addition of adding a specific handler
is made of. And using git blame will make it easier to find what content
was added by which commit.
See the attached files. They do not include text/x-calendar present in
the original patch. I am in doubts if it frequently appears in the wild.
thanks, I applied them locally. I rebased afterwards and sorted the
entries so they are ordered alphabetically. So it's better readable for
humans.
Frankly speaking, I have see a little value in splitting a commit that
changes just single line. I would not even try to add multiple MimeType
entries even if they would be supported by some frameworks. I believe
the comment was detailed enough to review entries of the list.
it's not about the comment, it's about traceability of modifications and
atomic commits.
It's far easier to revert things partially if needed if you handle
things in small enough peaces.
I decided to try git sparse-checkout and I was significantly more
optimistic how much data I have to get to make a series of commits
changing just single line. 1G is too much from my point of view. Perhaps
shallow clone could reduce it by several times.
Well the size of the packaging tree is rather big yes, but that is the
cost for holding all releases and work within one tree.
If you don't care much about all the history or all possible branches
you can pull in just the branch you want with quite zero history.
git clone --depth 1 $URL -b branchname
--
Regards
Carsten
