From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2008, #02; Sun, 14)
Date: Sun, 14 Dec 2008 03:08:24 -0800 (PST) [thread overview]
Message-ID: <m3prjvdngm.fsf@localhost.localdomain> (raw)
In-Reply-To: <7v7i632mg9.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.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've briefly looked at the resurrection of Ajaxy blame that comes on top
> of this series and it looked promising.
AJAXy blame in my opinion is not yet ready. Close, but not yet.
At minimal I'd have to remove or separate the 'time to generate'
patch.
I wonder if it should made into 1.6.1 for the performance improvements
in 'blame' view...
> * sc/gitweb-category (Fri Dec 12 00:45:12 2008 +0100) 3 commits
> - gitweb: Optional grouping of projects by category
> - gitweb: Split git_project_list_body in two functions
> - gitweb: Modularized git_get_project_description to be more generic
It shapes nicely, and I think with one more commit on top (or with
extending topmost commit) we can have categories sorted in given
order, and not hardcoded to always be in alphabetic order.
> ----------------------------------------------------------------
> [Post 1.6.1 items]
>
> * gb/gitweb-patch (Sat Dec 6 16:02:35 2008 +0100) 3 commits
> - gitweb: link to patch(es) view from commit and log views
> - gitweb: add patches view
> - gitweb: add patch view
>
> Updated series. Reviews and Acks?
I'll try to find time to review (and most probably Ack) later today.
> ----------------------------------------------------------------
> [Graduated to "master"]
>
> * 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
Isn't it in the same topic branch?
I am very sorry for buginess of this patch series...
[...]
> ----------------------------------------------------------------
> [On Hold]
>
> * jc/stripspace (Sun Mar 9 00:30:35 2008 -0800) 6 commits
> - git-am --forge: add Signed-off-by: line for the author
> - git-am: clean-up Signed-off-by: lines
> - stripspace: add --log-clean option to clean up signed-off-by:
> lines
> - stripspace: use parse_options()
> - Add "git am -s" test
> - git-am: refactor code to add signed-off-by line for the committer
What happened to this series to be so stale^Wstalled?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-12-14 11:09 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 [this message]
2008-12-15 6:16 ` Junio C Hamano
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=m3prjvdngm.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).