git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzesimir Nowak <krzesimir@endocode.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, jnareb@gmail.com, sunshine@sunshineco.com,
	Krzesimir Nowak <krzesimir@endocode.com>
Subject: [PATCH v7 0/4] Show extra branch refs in gitweb
Date: Wed, 11 Dec 2013 12:54:40 +0100	[thread overview]
Message-ID: <1386762884-7564-1-git-send-email-krzesimir@endocode.com> (raw)

First patch splits some code to a function.

Second patch fixes validation functions to return either 0 or 1,
instead of undef or passed $input.

Third patch adds the extra-branch-feature and some documentation.

Fourth patch adds some visual differentation of branches from
non-standard ref directories.

Krzesimir Nowak (4):
  gitweb: Move check-ref-format code into separate function
  gitweb: Return 1 on validation success instead of passed input
  gitweb: Add a feature for adding more branch refs
  gitweb: Denote non-heads, non-remotes branches

 Documentation/gitweb.conf.txt |  37 +++++++++
 gitweb/gitweb.perl            | 184 +++++++++++++++++++++++++++++++-----------
 2 files changed, 175 insertions(+), 46 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2013-12-11 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 11:54 Krzesimir Nowak [this message]
2013-12-11 11:54 ` [PATCH v7 1/4] gitweb: Move check-ref-format code into separate function Krzesimir Nowak
2013-12-11 11:54 ` [PATCH v7 2/4] gitweb: Return 1 on validation success instead of passed input Krzesimir Nowak
2013-12-11 16:08   ` Jakub Narębski
2013-12-11 11:54 ` [PATCH v7 3/4] gitweb: Add a feature for adding more branch refs Krzesimir Nowak
2013-12-11 11:54 ` [PATCH v7 4/4] gitweb: Denote non-heads, non-remotes branches Krzesimir Nowak
2013-12-12 21:46 ` [PATCH v7 0/4] Show extra branch refs in gitweb 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1386762884-7564-1-git-send-email-krzesimir@endocode.com \
    --to=krzesimir@endocode.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=sunshine@sunshineco.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).