From: Thiago Farina <tfransosi@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] commit: Add commit_list prefix to reduce_heads function.
Date: Sun, 5 Dec 2010 10:18:47 -0200 [thread overview]
Message-ID: <AANLkTinAT3kotKQTS6eS1SLigNzSp6grAU7WNRbHf3N=@mail.gmail.com> (raw)
In-Reply-To: <20101205021837.GA24614@burratino>
On Sun, Dec 5, 2010 at 12:18 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Thiago Farina wrote:
>
>> Signed-off-by: Thiago Farina <tfransosi@gmail.com>
>
> I know that the context is part of an effort to make the commit_list
> functions into something more of a self-contained API, but the
> reader does not know that. Perhaps you could say some words about
> that in the change description: what's wrong with the current
> situation, what context does this change come from, and what positive
> effect would it have?
>
> Beyond that, I must say I do not think this goes far enough to seem
> useful. If I wondered what reduce_heads did, wouldn't
> commit_list_reduce_heads be even more confusing? (ignoring the typo)
>
> Perhaps a more natural way to proceed would be as follows:
>
> . first, collect the functions to be treated as a module and
> list them in Documentation/technical (in this case, perhaps
> api-revision-walking or a new api-commit-list)
>
What you want here? That I describe the functions in these files? Why
me? Why not the person who wrote them?
> . next, describe their current meaning. If this requires
> apologizing for the name,
Apologize? For what? I don't understand what you mean here.
> that's a good hint that a name change might be worthwhile
>
> . finally, tweak signatures (names and arguments) based on the
> results from step 2 and update the documentation at the same
> time.
>
I'd prefer to do just that step.
> That way, people used to the current functions would at least have
> some documentation to help them adjust. What do you think?
>
I think it's a good procedure for someone more familiar with this
functions to do this. Perhaps, you or Junio?
next prev parent reply other threads:[~2010-12-05 12:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 1:59 [PATCH] commit: Add commit_list prefix to reduce_heads function Thiago Farina
2010-12-05 2:18 ` Jonathan Nieder
2010-12-05 12:18 ` Thiago Farina [this message]
2010-12-05 17:09 ` Jonathan Nieder
2010-12-05 17:29 ` Thiago Farina
2010-12-05 17:32 ` Thiago Farina
2010-12-05 21:07 ` Junio C Hamano
2010-12-05 21:29 ` Thiago Farina
2010-12-06 3:58 ` Junio C Hamano
2010-12-06 4:01 ` Junio C Hamano
2010-12-05 5:24 ` Junio C Hamano
2010-12-05 12:23 ` Thiago Farina
2010-12-05 20:40 ` 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='AANLkTinAT3kotKQTS6eS1SLigNzSp6grAU7WNRbHf3N=@mail.gmail.com' \
--to=tfransosi@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@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).