[PATCH] tracedump: add --help and --function-histogram

José Fonseca jose.r.fonseca at gmail.com
Fri Oct 21 00:57:03 PDT 2011


On Thu, Oct 20, 2011 at 10:43 PM, Carl Worth <cworth at cworth.org> wrote:
> On Thu, 20 Oct 2011 22:33:20 +0100, José Fonseca <jose.r.fonseca at gmail.com> wrote:
>> I can manage multiple repos easily. But can I push to
>> git://git.cworth.org/git/apitrace as well? I really don't wanna use
>> email for trivial things such as obvious bug fixes, or build fixes.
>
> No, you can't push there right now. But it's a false dichotomy to say
> that you would need to push to that repository or else resort to email.
>
> I can push my branches to my repository. You can push your branches,
> (built on top of mine, or rebased from my, or whatever), to your
> repositories.
>
>> For me the process that works the best is:
>> 1. you/somebody makes a branch with a feature
>> 2. you get the code to a point where it works minimailly
>> 3. you tell me it's ready for me to look at
>> 4. I review the code, I test on all platforms, and commit build fixes,
>> trivial bugfixes, etc. to the feature branch
>> 5. I may ask to do some further changes (e.g., fix regressions) which
>> take us back to step 2
>> 6. I merge the branch into master, and delete the feature branch
>
> All sounds fine to me. Step 3 would be pushed to my repository, step 4
> to yours, etc. Is that a problem?

It's no problem, simply sub-optimal AFAICS, as the split repositories
add complexity and for no benefit compared with simply collaborating
on a feature branch. But it's your contribution, so do whatever floats
your boat.

It's ironic that most people wanna commit access to community
repositories, and here I am trying to convince you to take it :)

Jose


More information about the apitrace mailing list