From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH/RFC] gitweb: Great subroutines renaming
Date: Thu, 10 Aug 2006 09:57:04 +0200 [thread overview]
Message-ID: <ebeorr$amq$1@sea.gmane.org> (raw)
In-Reply-To: 7v3bc5397r.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> Subroutines in gitweb: <current name> => <proposed rename>.
>
> If it is not too much trouble, having a few line summary of what
> each of the sub does would greatly help judging if the names are
> appropriate.
Subroutines name guideline, revised:
* git_ prefix for subroutines related to git commands,
or to gitweb actions
* git_get_ prefix for inner subroutines calling git command
and returning some output
* parse_ prefix for subroutines parsing some text, or reading and
parsing some text into hash or list
* format_ prefix for subroutines formatting/post-processing some
HTML/text fragment
* _get_ infix for subroutines which return result
* _print_ infix for subroutines which print fragment of output
* _body suffix for subroutines which outputs main part (body)
of related action
* _nav suffix for subroutines related to navigation bars
* _div suffix for subroutines returning or printing div element
Current gitweb subroutines, with proposed renames, and short summary.
* validate_input => is_valid_ref, is_valid_path (?)
universal (too universal) parameter validation
* esc_param
quote unsafe chars in link parameters
* esc_html
escape to HTML, replace invalid uft8 characters
* unquote
unquote filenames quoted and escaped by git
* untabify
convert tabs (8 spaces wide tabstops) to spaces
* chop_str
shorten string, removing characters entities as whole
* age_class
CSS class for given age value (in seconds)
* age_string
convert age in seconds to "nn units ago" string
* mode_str
convert file mode in octal to symbolic file mode string
* file_type
convert file mode in octal to file type string (directory, symlink,
file, unknown)
* format_log_line_html
format line of commit message or tag comment, hyperlinking commitids
(perhaps in the future comittags, e.g. BUG(nn) support)
* git_get_referencing => format_mark_referencing (???)
return HTML fragment generating marker of refs pointing to given object
* git_read_head => git_get_head_hash
get HEAD ref of given project as hash
* git_read_hash => git_get_hash_by_ref
get hash of given ref (e.g. refs/heads/next)
* git_get_hash_by_path
get hash of given path at given ref
* git_get_type
get type of given object (by hash)
* git_get_project_config
return value of given variable in gitweb section
* git_get_project_config_bool
return value of given variable in gitweb section, as boolean
* git_read_description => git_get_project_description
* git_read_projects => git_get_projects_list
return list of projects (path, owner)
* read_info_ref => git_get_references
return hashref of refs pointing to object given by hash key
* git_read_refs => git_get_refs_list
list of hashrefs of parsed ref info
(parsing to be separated into parse_ref subroutine)
* date_str => parse_date
given epoch and (optionally) timezone return parsed date as hash
* git_read_tag => parse_tag
given tag_id, return parsed tag as Perl hash
* git_read_commit => parse_commit
given commit_id (and optionally commit_text to reuse), return parsed
commit
* get_file_owner
return owner of given file, according to user id and gcos field
* mimetype_guess_file => ???
reads and parses mime.types like file, return mimetype of given filename
* mimetype_guess => (to be incorporated in blob_mimetype)
try $mimetypes_file, or /etc/mime.types
* git_blob_plain_mimetype => blob_mimetype
return mimetype of given (by file descriptor and filename) blob
* git_get_paging_nav => ???
return HTML fragment generating "HEAD * prev * next" page navigation
* git_page_nav => git_print_page_nav
print "action" navigation bar, optionally with pager or formats below
* git_header_div => git_print_header_div
prints div element of class "header" just below navigation bar
* git_print_page_path
print div element of class "page_path" with current path
* git_diff_print => (to be made obsolete)
print diff between two files, using /usr/bin/diff and temporary files
* git_header_html
prints HTML header of gitweb output
* git_footer_html
prints HTML footer of gitweb output
* die_error
prints gitweb error page
Subroutines printing table with shortlog, tags, heads respectively
* git_shortlog_body
* git_tags_body
* git_heads_body
Action subroutines
* git_project_list
* git_summary
* git_tag
* git_blame2 => git_blame (?)
* git_blame => git_annotate (?)
* git_tags
* git_heads
* git_blob_plain
* git_blob
* git_tree
* git_log
* git_commit
* git_blobdiff
* git_blobdiff_plain
* git_commitdiff
* git_commitdiff_plain
* git_history
* git_search
* git_shortlog
* git_rss
* git_opml
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-10 7:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 14:26 [PATCH/RFC] gitweb: Great subroutines renaming Jakub Narebski
2006-08-07 19:37 ` Junio C Hamano
2006-08-07 21:47 ` Jakub Narebski
2006-08-07 21:52 ` Jakub Narebski
2006-08-07 22:00 ` Junio C Hamano
2006-08-07 22:15 ` Jakub Narebski
2006-08-07 22:58 ` Jakub Narebski
2006-08-07 23:49 ` Junio C Hamano
2006-08-08 0:10 ` Jakub Narebski
2006-08-08 9:38 ` Jakub Narebski
2006-08-08 20:18 ` Junio C Hamano
2006-08-08 20:24 ` Jakub Narebski
2006-08-08 9:51 ` Jakub Narebski
2006-08-08 18:12 ` git-show-refs (was: [PATCH/RFC] gitweb: Great subroutines renaming) Jakub Narebski
2006-08-09 10:26 ` [PATCH/RFC] gitweb: Great subroutines renaming Jakub Narebski
2006-08-09 10:51 ` Junio C Hamano
2006-08-09 11:01 ` Jakub Narebski
2006-08-09 11:11 ` Junio C Hamano
2006-08-08 9:48 ` Jakub Narebski
2006-08-08 21:13 ` Jakub Narebski
2006-08-08 21:50 ` Junio C Hamano
2006-08-08 22:33 ` Jakub Narebski
2006-08-09 20:54 ` Jakub Narebski
2006-08-09 21:11 ` Junio C Hamano
2006-08-10 7:57 ` Jakub Narebski [this message]
2006-08-12 23:09 ` Jakub Narebski
2006-08-13 2:21 ` Junio C Hamano
2006-08-13 2:27 ` Junio C Hamano
2006-08-13 9:29 ` Jakub Narebski
2006-08-14 0:11 ` 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='ebeorr$amq$1@sea.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.