git-commit-vandalism

Git with broken hash generation to generate collisions between object IDs. Don't use this! https://undefinedbehavior.de/posts/commit-vandalism/

Go to file

Kay Sievers 40c138134f replace invalid utf8 sequences by UTF-8 REPLACEMENT CHARACTER (efbfbd) I still strongly disagree with the git maintainers not to hint people, to use the only sane default encoding for a distributed project, which is utf8. I'm tired of hearing filesystem development arguments. Git is a software offered to merge forth and back across the world and not to provide a content neutral filesystem. Btw: I have nothing against the ability to run git in a closed environment, with a different encoding, that's fine, sure. But that is obviously not the case for the projects on kernel.org. It's about sane defaults, nothing else. You have to make decisions guy, as always in life. The problems to allow random encoded garbage in commit messages _without_ storing the encoding, just makes zero sense. Eighter you introduce a per-commit encoding field, if you insist on this craziness, or you define a default encoding. Everything else is just lazy and does not solve any problem, besides that you can claim now, that you are not responsible for the mess in the repository. Gitweb shows several commits at once, you allow various encodings committed to the same repository, without any hint what that garbage from the individual commits is encoded with. No idea why you don't get the problem - it's unsolvable. If you merge different peoples work, you have to speak a common language! Kay Sievers <kay.sievers@vrfy.org>	2005-11-19 17:41:29 +01:00
test	update the test files to have a diff	2005-11-14 05:45:31 +01:00
gitweb.cgi	replace invalid utf8 sequences by UTF-8 REPLACEMENT CHARACTER (efbfbd)	2005-11-19 17:41:29 +01:00
README	add README	2005-08-07 22:39:58 +02:00

Kay Sievers 40c138134f replace invalid utf8 sequences by UTF-8 REPLACEMENT CHARACTER (efbfbd)

I still strongly disagree with the git maintainers not to hint people,
to use the only sane default encoding for a distributed project,
which is utf8. I'm tired of hearing filesystem development arguments.
Git is a software offered to merge forth and back across the world
and not to provide a content neutral filesystem.
Btw: I have nothing against the ability to run git in a closed environment,
with a different encoding, that's fine, sure. But that is obviously not
the case for the projects on kernel.org. It's about sane defaults,
nothing else.

You have to make decisions guy, as always in life. The problems to
allow random encoded garbage in commit messages _without_ storing
the encoding, just makes zero sense. Eighter you introduce a per-commit
encoding field, if you insist on this craziness, or you define a default
encoding. Everything else is just lazy and does not solve any problem,
besides that you can claim now, that you are not responsible for the mess
in the repository.

Gitweb shows several commits at once, you allow various encodings committed
to the same repository, without any hint what that garbage from the
individual commits is encoded with. No idea why you don't get
the problem - it's unsolvable. If you merge different peoples work, you
have to speak a common language!

Kay Sievers <kay.sievers@vrfy.org>

2005-11-19 17:41:29 +01:00

test

update the test files to have a diff

2005-11-14 05:45:31 +01:00

gitweb.cgi

replace invalid utf8 sequences by UTF-8 REPLACEMENT CHARACTER (efbfbd)

2005-11-19 17:41:29 +01:00

README

add README

2005-08-07 22:39:58 +02:00

README

GIT web Interface

The one working on:
  http://www.kernel.org/git/

Get the gitweb.cgi by ftp:
  ftp://ftp.kernel.org/pub/software/scm/gitweb/

It reqires the git-core binaries installed on the system:
  http://www.kernel.org/git/?p=git/git.git;a=summary

The gitweb repository is here:
  http://www.kernel.org/git/?p=git/gitweb.git;a=summary

Any comment/question/concern to:
  Kay Sievers <kay.sievers@vrfy.org>