From: Junio C Hamano <gitster@pobox.com>
To: Drew Northup <n1xim.email@gmail.com>
Cc: git@vger.kernel.org, "Jakub Narębski" <jnareb@gmail.com>,
"Jürgen Kreileder" <jk@blackdown.de>
Subject: Re: What's cooking in git.git (Jun 2013, #01; Sun, 2)
Date: Mon, 01 Jul 2013 15:05:04 -0700 [thread overview]
Message-ID: <7vip0uaq02.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: CAM9Z-nmk1qfQZLCH1g2DVaZXm+WY03oTr19ZRZ8L9rb1apSz6Q@mail.gmail.com
Drew Northup <n1xim.email@gmail.com> writes:
> On Sun, Jun 2, 2013 at 7:58 PM, Junio C Hamano <gitster@pobox.com> wrote:
> ...
>> --------------------------------------------------
>> [Stalled]
> ...
>> * jk/gitweb-utf8 (2013-04-08) 4 commits
>> - gitweb: Fix broken blob action parameters on blob/commitdiff pages
>> - gitweb: Don't append ';js=(0|1)' to external links
>> - gitweb: Make feed title valid utf8
>> - gitweb: Fix utf8 encoding for blob_plain, blobdiff_plain, commitdiff_plain, and patch
>>
>> Various fixes to gitweb.
>>
>> Waiting for a reroll after a review.
>> Will discard unless we hear from anybody who is interested in
>> tying its loose ends.
>
> I'd like to have a closer look at these. It may be a week however as
> there's some serious in-house chaos going on right now. (Finally
> starting to settle after about 2 months...)
Ping? No need to hurry but in case somebody else is interested but
is stopped because of this offer to review...
Thanks.
next prev parent reply other threads:[~2013-07-01 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 23:58 What's cooking in git.git (Jun 2013, #01; Sun, 2) Junio C Hamano
2013-06-03 0:35 ` Jiang Xin
2013-06-03 18:30 ` Junio C Hamano
2013-06-03 11:23 ` Antoine Pelisse
2013-06-03 15:28 ` Junio C Hamano
2013-06-03 12:10 ` Drew Northup
2013-06-03 15:28 ` Junio C Hamano
2013-07-01 22:05 ` Junio C Hamano [this message]
2013-06-03 13:23 ` Duy Nguyen
2013-06-03 15:29 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vip0uaq02.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jk@blackdown.de \
--cc=jnareb@gmail.com \
--cc=n1xim.email@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).