From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH/RFC] gitweb: Great subroutines renaming
Date: Wed, 09 Aug 2006 22:54:42 +0200 [thread overview]
Message-ID: <ebdi1v$cv5$1@sea.gmane.org> (raw)
In-Reply-To: ebb3fm$2md$1@sea.gmane.org
Subroutines in gitweb: <current name> => <proposed rename>.
If nobody would give any better suggestions, or warn about patches to gitweb
to be sent, could we do that "Great subroutines renaming" some time soon?
TIA.
* validate_input
* esc_param
* esc_html
* unquote
* untabify
* chop_str
* age_class
* age_string
* mode_str
* file_type
* format_log_line_html
* git_get_referencing => format_mark_referencing (???)
* git_read_head => git_get_head_hash
* git_read_hash => git_get_hash_by_ref
* git_get_hash_by_path
* git_get_type
* git_get_project_config
* git_get_project_config_bool
* git_read_description => git_get_project_description
* git_read_projects => git_get_projects_list
* read_info_ref => git_get_references
* git_read_refs => git_get_refs_list
* date_str => parse_date
* git_read_tag => parse_tag
* git_read_commit => parse_commit
* get_file_owner
* mimetype_guess_file => ??? (reads, parses and uses mime.types like file)
* mimetype_guess => (to be incorporated in blob_mimetype)
* git_blob_plain_mimetype => blob_mimetype
* git_get_paging_nav => ???
* git_page_nav => git_print_page_nav
* git_header_div => git_print_header_div
* git_print_page_path
* git_diff_print => (to be made obsolete)
* git_header_html
* git_footer_html
* die_error
* git_shortlog_body
* git_tags_body
* git_heads_body
* 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-09 20:54 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 [this message]
2006-08-09 21:11 ` Junio C Hamano
2006-08-10 7:57 ` Jakub Narebski
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='ebdi1v$cv5$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 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).