Git development
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Mark Rada <marada@uwaterloo.ca>, Jakub Narebski <jnareb@gmail.com>
Subject: [PATCHv2 0/3] gitweb: Smarter snapshot names
Date: Sat,  7 Nov 2009 16:13:26 +0100	[thread overview]
Message-ID: <1257606809-23287-1-git-send-email-jnareb@gmail.com> (raw)

This is the replacement for 'mr/gitweb-snapshot' branch (aba1076),
currently in 'pu'.

Compared to previous series the t9502-gitweb-standalone-parse-output
test is created in earlier commit, to better show changes in snapshot
behaviour in "gitweb: Smarter snapshot names".

The first commit in series is identical to the one in previous version
of this series.  Changes in last commit in series are only about
tests.

Shortlog:
~~~~~~~~~
Jakub Narebski (2):
  t/gitweb-lib.sh: Split gitweb output into headers and body
  gitweb: Document current snapshot rules via new tests

Mark Rada (1):
  gitweb: Smarter snapshot names

Table of contents:
~~~~~~~~~~~~~~~~~~
 [PATCH 1/3] t/gitweb-lib.sh: Split gitweb output into headers and body
 [PATCH 2/3] gitweb: Document current snapshot rules via new tests
 [PATCH 3/3] gitweb: Smarter snapshot names

Diffstat:
~~~~~~~~~
 gitweb/gitweb.perl                        |   76 +++++++++++++++----
 t/gitweb-lib.sh                           |    6 +-
 t/t9502-gitweb-standalone-parse-output.sh |  115 +++++++++++++++++++++++++++++
 3 files changed, 180 insertions(+), 17 deletions(-)
 create mode 100755 t/t9502-gitweb-standalone-parse-output.sh

-- 
Jakub Narebski
Poland

             reply	other threads:[~2009-11-07 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-07 15:13 Jakub Narebski [this message]
2009-11-07 15:13 ` [PATCH 1/3] t/gitweb-lib.sh: Split gitweb output into headers and body Jakub Narebski
2009-11-07 15:13 ` [PATCH 2/3] gitweb: Document current snapshot rules via new tests Jakub Narebski
2009-11-07 15:13 ` [PATCHv7 3/3] gitweb: Smarter snapshot names 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=1257606809-23287-1-git-send-email-jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=marada@uwaterloo.ca \
    /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