git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH 0/2] gitweb: Simplify dealing with raw diff output
Date: Thu,  1 Nov 2007 12:38:07 +0100	[thread overview]
Message-ID: <1193917089-15920-1-git-send-email-jnareb@gmail.com> (raw)

This series of patches simplifies (and improves) gitweb code dealing
with (parsed) raw diff output format.

See individual patches for more detail.


Table of contents:
 [PATCH 1/2] gitweb: Always set 'from_file' and 'to_file'
             in parse_difftree_raw_line 
 [PATCH 2/2] gitweb: Add 'status_str' to parse_difftree_raw_line output

Diffstat:
 gitweb/gitweb.perl |   22 +++++++++++++---------
 1 files changed, 13 insertions(+), 9 deletions(-)

-- 
Jakub Narebski
Poland

             reply	other threads:[~2007-11-01 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 11:38 Jakub Narebski [this message]
2007-11-01 11:38 ` [PATCH 1/2] gitweb: Always set 'from_file' and 'to_file' in parse_difftree_raw_line Jakub Narebski
2007-11-01 22:47   ` Junio C Hamano
2007-11-01 23:46     ` Jakub Narebski
2007-11-01 11:38 ` [PATCH 2/2] gitweb: Add 'status_str' to parse_difftree_raw_line output 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=1193917089-15920-1-git-send-email-jnareb@gmail.com \
    --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 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).