From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH/RFC] gitweb: Great subroutines renaming
Date: Tue, 08 Aug 2006 02:10:33 +0200 [thread overview]
Message-ID: <eb8kph$j6i$1@sea.gmane.org> (raw)
In-Reply-To: 7vejvsyum8.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>> So the new guidelines would be:
>> * git_get_ prefix for subroutines related to git repository
>> and returning single scalar (single value).
>> * git_read_ prefix for subroutines related to git repository, reading some
>> files or multiline output, and returning hash reference, or list
>> reference, or list.
>
> I would suggest to use git_get for both, unless there is a good
> reason to differenciate them, since I do not understand why you
> would want to differenciate one value vs multivalue.
I'd rather have git_read_info_refs, because it _reads_ info/refs file,
and git_read_refs as opposed to git_get_hash/git_get_ref/git_ref_to_hash
(or hash_from_ref). I'm not sure about git_read_projects vs. perhaps
git_get_project_list or git_list_projects. Neither about
git_read_description vs. git_get_project_description
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-08 0:10 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 [this message]
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
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='eb8kph$j6i$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.