All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2008, #05; Wed, 22)
Date: Fri, 24 Oct 2008 15:45:11 +0200	[thread overview]
Message-ID: <gdsjb1$eob$1@ger.gmane.org> (raw)
In-Reply-To: 7v8wsf50ne.fsf@gitster.siamese.dyndns.org

Junio C Hamano wrote:

> * gb/gitweb-pathinfo (Tue Oct 21 21:34:54 2008 +0200) 5 commits
>  - gitweb: generate parent..current URLs
>  - gitweb: parse parent..current syntax from PATH_INFO
>  - gitweb: use_pathinfo filenames start with /
>  - gitweb: generate project/action/hash URLs
>  - gitweb: parse project/action/hash_base:filename PATH_INFO
> 
> Seventh iteration; hopefully the usual gitweb gangs will give quick
> comments and ack to push this out to 'next' soon.

If I remember correctly v7 is mainly cosmetic changes, and I have
acked all or almost all of the equivalent patches from v6.
 
> * gb/refactor-pathinfo (Fri Oct 10 20:42:26 2008 +0200) 1 commit
>  + gitweb: refactor input parameters parse/validation
> 
> A major cleanup on the way gitweb parses its input arguments.
> Future gitweb patches to add more arguments into the PATH_INFO
> depend upon this initial cleanup work.

Nice.

> * jn/gitweb-customlinks (Sun Oct 12 00:02:32 2008 +0200) 1 commit
>  - gitweb: Better processing format string in custom links in navbar
> 
> Waiting for some sort of response from Pasky.
> 
> * jc/gitweb-fix-cloud-tag (Tue Oct 14 21:27:12 2008 -0700) 1 commit
>  + Fix reading of cloud tags
> 
> Request-for-review-and-ack sent; waiting for response.

It would be nice to have those two...

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2008-10-24 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23  5:41 What's cooking in git.git (Oct 2008, #05; Wed, 22) Junio C Hamano
2008-10-24 13:45 ` Jakub Narebski [this message]
2008-10-24 22:13   ` Junio C Hamano
2008-10-24 23:06     ` Jakub Narebski

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='gdsjb1$eob$1@ger.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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.