From: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
To: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: gitweb: how to name main "action" subroutines?
Date: Mon, 31 Jul 2006 20:38:44 +0200 [thread overview]
Message-ID: <200607312038.44337.Josef.Weidendorfer@gmx.de> (raw)
In-Reply-To: <eal2ic$14o$1@sea.gmane.org>
On Monday 31 July 2006 16:03, you wrote:
> I'm going to rename some gitweb subroutines to better correspond to what
> given subroutine does. I have problem: how to name main "action"
> subroutines? Currently they use git_ prefix, e.g. git_logo.
> git_project_list, git_rss, git_summary, git_heads,...
print_* or write_* ?
At least, the functions print/write the HTML code to stdout of the script.
Josef
>
> I have thought about do_logo, or gitweb_logo, or out_logo etc., but somehow
> none is best.
next prev parent reply other threads:[~2006-07-31 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 14:03 gitweb: how to name main "action" subroutines? Jakub Narebski
2006-07-31 17:26 ` Luben Tuikov
2006-07-31 17:50 ` Jakub Narebski
2006-07-31 18:38 ` Josef Weidendorfer [this message]
2006-07-31 18:45 ` Jakub Narebski
2006-07-31 20:41 ` Josef Weidendorfer
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=200607312038.44337.Josef.Weidendorfer@gmx.de \
--to=josef.weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@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.
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).