v260
attach tag to the link
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v259
show multiple tags
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v258
show tags in lists
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v257
fix "rename" output
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v256
fix quoted filename lookup
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v255
v254
allow utf8 characters in url parameter escape
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v253
set logo output to raw mode
add broken latin encoding to test file
add ut8 test file
It contains Märchen. (\xc3a4)
It contains Märchen. (\xc3a4)
fix utf8 decoding
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v252
fix another typo
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v251
add missing esc() rename
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v250
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>
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>
escape ' ' with '+' in url's
v249
make ' ' and '+' in filenames some kind of working
escape '+' and ' ' in url's
update the test files to have a diff
add test files
v248
add Expires: +1d header to commit and commitdiff pages
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
provide filename for "save as" in plaintext views
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v247
rename "branches" to "heads"
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v246
start searching at the current $hash value
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v245
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
switch to git-rev-list for commit reading
This way we don't need to parse the "grafts".
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
This way we don't need to parse the "grafts".
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v244
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
fix typo in link parameter of git_commit
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
translate reference into hash while reading a commit
v243
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
common input validation to allow passing of textual hash id's
v242
fix typo
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
fix typo
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
v241
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Show tooltips (like this one :)) containing full titles for truncated commit titles in the summary and shortlog views.
Thanks for the patch to:
Timo Hirvonen <tihirvon at gmail.com>
Thanks for the patch to:
Timo Hirvonen <tihirvon at gmail.com>
don't chop_str if adding ... is longer than the original
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Add <author> and <guid> to RSS feed
From http://blogs.law.harvard.edu/tech/rss
author - Email address of the author of the item.
guid - A string that uniquely identifies the item.
Signed-off-by: Yasushi SHOJI <yashi@atmark-techno.com>
From http://blogs.law.harvard.edu/tech/rss
author - Email address of the author of the item.
guid - A string that uniquely identifies the item.
Signed-off-by: Yasushi SHOJI <yashi@atmark-techno.com>
fix search parsing, later git does not print a trailing space
make index page sorting more visible and increase RSS item count
The RSS feed now shows 30 items + all items more recent than 48 hours
but not more than 150. Let's see how that works...
The RSS feed now shows 30 items + all items more recent than 48 hours
but not more than 150. Let's see how that works...
allow sorting of index page by project path, owner and age
Make the tag view look like commit header.
add README
Two files are better than one. :)
Two files are better than one. :)
v236
v235
v234
v233
v232
v229
v227
v225
v220
v206
v205
v203
v165
v164
v163
v160
v157
v154
v152
v150
v149
v148
v145
v143
v142
v136
v133
v125
v121
v118
v107
v089
v088
v085
v082
v080
v078
v077
v073
v071
v070
v064
v063
v062
v057
v056