<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/git.git/gitweb/gitweb.perl, branch v1.5.6.4</title>
<subtitle>Git
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.5.6.4</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.5.6.4'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/'/>
<updated>2008-06-17T23:39:18Z</updated>
<entry>
<title>gitweb: remove unused parse_ref method</title>
<updated>2008-06-17T23:39:18Z</updated>
<author>
<name>Lea Wiemann</name>
<email>lewiemann@gmail.com</email>
</author>
<published>2008-06-17T06:25:28Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=61fb0b75d138032c7600fe86640897b900f2fd4f'/>
<id>urn:sha1:61fb0b75d138032c7600fe86640897b900f2fd4f</id>
<content type='text'>
The parse_ref method became unused in cd1464083c, but the author
decided to leave it in.  Now it gets in the way of refactoring, so
let's remove it.

Signed-off-by: Lea Wiemann &lt;LeWiemann@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gitweb: quote commands properly when calling the shell</title>
<updated>2008-06-17T23:39:09Z</updated>
<author>
<name>Lea Wiemann</name>
<email>lewiemann@gmail.com</email>
</author>
<published>2008-06-17T21:46:35Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=516381d50ba7acb66f260461f4d566ab9b6df107'/>
<id>urn:sha1:516381d50ba7acb66f260461f4d566ab9b6df107</id>
<content type='text'>
This eliminates the function git_cmd_str, which was used for composing
command lines, and adds a quote_command function, which quotes all of
its arguments (as in quote.c).

Signed-off-by: Lea Wiemann &lt;LeWiemann@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gitweb: Make it work with $GIT containing spaces</title>
<updated>2008-06-14T19:48:06Z</updated>
<author>
<name>Jakub Narebski</name>
<email>jnareb@gmail.com</email>
</author>
<published>2008-06-14T18:37:59Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=66115d363a93b9e7c9b937773c0c30f81b766d45'/>
<id>urn:sha1:66115d363a93b9e7c9b937773c0c30f81b766d45</id>
<content type='text'>
This fixes single point where $GIT (which can contain full path
to git binary) with embedded spaces gave errors.

Signed-off-by: Jakub Narebski &lt;jnareb@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gitweb: Add charset info to "raw" output of 'text/plain' blobs</title>
<updated>2008-06-04T22:05:01Z</updated>
<author>
<name>Jakub Narebski</name>
<email>jnareb@gmail.com</email>
</author>
<published>2008-06-03T14:47:10Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=7f718e8b46b37a9e1caf58a372938817f04885d9'/>
<id>urn:sha1:7f718e8b46b37a9e1caf58a372938817f04885d9</id>
<content type='text'>
Earlier "blob_plain" view sent "charset=utf-8" only when gitweb
guessed the content type to be text by reading from it, and not when
the MIME type was obtained from /etc/mime.types, or when gitweb
couldn't guess mimetype and used $default_blob_plain_mimetype.

This fixes the bug by always add charset info from
$default_text_plain_charset (if it is defined) to "raw" (a=blob_plain)
output for 'text/plain' blobs.

Generating information for Content-Type: header got separated into
blob_contenttype() subroutine; adding charset info in a special case
was removed from blob_mimetype(), which now should return mimetype
only.

While at it cleanup code a bit: put subroutine parameter
initialization first, make error message more robust (when $file_name
is not defined) if more cryptic, remove unnecessary '"' around
variable ("$var" -&gt; $var).

Signed-off-by: Jakub Narebski &lt;jnareb@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gitweb: Fix "next" link on bottom of page</title>
<updated>2008-06-03T03:36:02Z</updated>
<author>
<name>Jakub Narebski</name>
<email>jnareb@gmail.com</email>
</author>
<published>2008-06-02T09:54:41Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=f70dda250e33dd17f6fdff17d15287391d8b0952'/>
<id>urn:sha1:f70dda250e33dd17f6fdff17d15287391d8b0952</id>
<content type='text'>
Fix search form generation to not modify $cgi-&gt;param(...)'s.

In git_header_html() we used to use $cgi-&gt;hidden(-name =&gt; "a") etc. to
generate hidden fields; unfortunately to use this form it is required
to modify $cgi-&gt;param("a") etc., which makes href(-replay,...) use
wrong replay values.  This for example made the "next" link on the
bottom of the page has a=search instead of a=$action, and thus fails to
get you to the next page.

Because in CGI the value of a hidden field is "sticky", there is no
way to modify it short of modifying $cgi-&gt;param(...).  Therefore it
got replaced by generating &lt;input type="hidden" ...&gt; element [semi]
directly.

Alternate solution would be for href(-replay,...) to use values saved
in global variables, such as $action etc., instead of (re)reading them
from $cgi-&gt;param($symbol).

The bad link was reported by Kai Blin through
  http://bugs.debian.org/481902

Reported-by: Kai Blin &lt;kai.blin@gmail.com&gt;
Signed-off-by: Jakub Narebski &lt;jnareb@gmail.com&gt;
Tested-by: Gerrit Pape &lt;pape@smarden.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge 1.5.5.3 in</title>
<updated>2008-05-28T05:34:19Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-05-28T05:22:47Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=b71ce7f3f13ebd0e212bdda82b012ee36df4f63f'/>
<id>urn:sha1:b71ce7f3f13ebd0e212bdda82b012ee36df4f63f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>gitweb: only display "next" links in logs if there is a next page</title>
<updated>2008-05-28T05:27:30Z</updated>
<author>
<name>Lea Wiemann</name>
<email>lewiemann@gmail.com</email>
</author>
<published>2008-05-27T23:25:42Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=1f684dc01c6a45341e8e47d8393f0ef66fdfc398'/>
<id>urn:sha1:1f684dc01c6a45341e8e47d8393f0ef66fdfc398</id>
<content type='text'>
There was a bug in the implementation of the "next" links in
format_paging_nav (for log and shortlog), which caused the next links
to always be displayed, even if there is no next page.  This fixes it.

Signed-off-by: Lea Wiemann &lt;LeWiemann@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gitweb: Convert string to internal form before chopping in chop_str</title>
<updated>2008-05-23T06:03:43Z</updated>
<author>
<name>Anders Waldenborg</name>
<email>anders@0x63.nu</email>
</author>
<published>2008-05-21T11:44:43Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=dee2775a29440ca8a52bb5bd09a6de6cd29f69cc'/>
<id>urn:sha1:dee2775a29440ca8a52bb5bd09a6de6cd29f69cc</id>
<content type='text'>
Fix chop_str not to cut in middle of utf8 multibyte chars. Without
this fix at least author name in short log may cut in middle of a
multibyte char. When the result comes to esc_html to_utf8 is called
again, which doesn't find valid utf8 and decodes using
$fallback_encoding making it even worse.

This also have the nice side effect that it actually tries to show the
first 10 _characters_, not the number of characters that happened to fit
into 10 bytes.

Signed-off-by: Anders Waldenborg &lt;anders@0x63.nu&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>gitweb: Use feed link according to current view</title>
<updated>2008-04-27T00:48:48Z</updated>
<author>
<name>Jakub Narebski</name>
<email>jnareb@gmail.com</email>
</author>
<published>2008-04-20T20:09:48Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=3562198b7da7ef6597af27b3a7fcaeee41608999'/>
<id>urn:sha1:3562198b7da7ef6597af27b3a7fcaeee41608999</id>
<content type='text'>
Michael G. Noll said in comments to the "Switching my code repository from
Subversion (SVN) to git" article (http://tinyurl.com/37v67l) in his "My
digital moleskine" blog, that one of the things he is missing in gitweb
from SVN::Web is an RSS feed with news/information of the current view
(including RSS feed for single file or directory).

This is not exactly true, as since refactoring feed generation in af6feeb
(gitweb: Refactor feed generation, make output prettier, add Atom feed,
2006-11-19), gitweb can generate feeds (RSS or Atom) for history of a
given branch, history limited to a given directory, or history of a given
file.  Nevertheless this required handcrafting the URL to get wanted RSS
feed.

This commit makes gitweb select feed links in the HTML header and in
page footer depending on current view (action).  It is more elaborate,
and I guess more correct, than simple patch adding $hash ('h')
parameter to *all* URLs, including feed links, by Jean-Baptiste Quenot

  Subject: [PATCH] gitweb: Add hash parameter in feed URL when a hash
           is specified in the current request
  Message-ID: &lt;ae63f8b50803211138y6355fd11pa64cda50a1f53011@mail.gmail.com&gt;

If $hash ('h') or $hash_base ('hb') parameter is a branch name
(i.e. it starts with 'refs/heads/'; all generated URLs use this form
to discriminate between tags and heads), it is used in feed URLs; if
$file_name ('f') is defined, it is used in feed URLs.  Feed title is
set according to the kind of web feed: it is either 'log' for generic
feed, 'log of &lt;branch&gt;', 'history of &lt;filename&gt;' for generic history
(using implicit or explicit HEAD, i.e. current branch) or 'history of
&lt;filename&gt; on &lt;branch&gt;'.

There are special cases: 'heads' and 'forks' views should use OPML
providing list of available feeds; 'tags' probably also should use
OPML; there is no web feed equivalent to 'search' view.  Currently all
those cases fallback to (show) default feed.  Such feed link uses
"generic" class, and is shown in slightly lighter color for
distinction.

Currently feed can have but one starting point, and does not support
negative (exclude) commit arguments.  Therefore for now for *diff
views it is chosen that feed follow the "to" part: to-name, to-commit
for 'blobdiff', 'treediff' and 'commitdiff' views.

Generating parameters for href() for feed link was separated
(refactored) into get_feed_info() subroutine.

Signed-off-by: Jakub Narebski &lt;jnareb@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2008-04-22T07:10:20Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-04-22T07:10:20Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=bdb87afb4b425d97f7b5e957cbed1589969d9a24'/>
<id>urn:sha1:bdb87afb4b425d97f7b5e957cbed1589969d9a24</id>
<content type='text'>
* maint:
  post-receive-email: fix accidental removal of a trailing space in signature line
  Escape project names before creating pathinfo URLs
  Escape project name in regexp
  bash: Add completion for git diff --base --ours --theirs
  diff-options.txt: document the new "--dirstat" option
</content>
</entry>
</feed>
