From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2008, #02; Sun, 14)
Date: Sun, 14 Dec 2008 22:16:17 -0800 [thread overview]
Message-ID: <7vabayynda.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: m3prjvdngm.fsf@localhost.localdomain
Jakub Narebski <jnareb@gmail.com> writes:
>> [New Topics]
>>
>> * jn/gitweb-blame (Thu Dec 11 01:33:29 2008 +0100) 3 commits
>> - gitweb: cache $parent_commit info in git_blame()
>> - gitweb: A bit of code cleanup in git_blame()
>> - gitweb: Move 'lineno' id from link to row element in git_blame
>
> I wonder if it should made into 1.6.1 for the performance improvements
> in 'blame' view...
Does is addresses a grave bug? I thought not.
>> [Post 1.6.1 items]
>>
>> * gb/gitweb-patch (Sat Dec 6 16:02:35 2008 +0100) 3 commits
>> Updated series. Reviews and Acks?
>
> I'll try to find time to review (and most probably Ack) later today.
Thanks.
>> * jn/gitweb-utf8 (Mon Dec 1 19:01:42 2008 +0100) 1 commit
>> + gitweb: Fix handling of non-ASCII characters in inserted HTML
>> files.
>>
>> A bugfix.
>
> What about
>
> + gitweb: Fix bug in insert_file() subroutine
It already is part of 'master' for some time, isn't it?.
>> * jc/stripspace (Sun Mar 9 00:30:35 2008 -0800) 6 commits
> ...
> What happened to this series to be so stale^Wstalled?
Mostly lack of positive feedbacks which is the same thing as "nobody but
the author is interested'.
next prev parent reply other threads:[~2008-12-15 6:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 8:24 What's cooking in git.git (Dec 2008, #02; Sun, 14) Junio C Hamano
2008-12-14 10:44 ` Johannes Schindelin
2008-12-14 11:15 ` Jeff King
2008-12-14 11:24 ` Johannes Schindelin
2008-12-14 11:17 ` Jakub Narebski
2008-12-14 13:15 ` Miklos Vajna
2008-12-14 11:08 ` Jakub Narebski
2008-12-15 6:16 ` Junio C Hamano [this message]
2008-12-15 19:59 ` Daniel Barkalow
2008-12-16 1:35 ` Nguyen Thai Ngoc Duy
2008-12-16 1:42 ` Junio C Hamano
2008-12-16 3:36 ` Daniel Barkalow
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=7vabayynda.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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.