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

[Carl Worth]

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 important to realize that by the time the branch is merged no
> feature should regress on any of the platforms.

Sounds good. So "apitrace" would be a new tool so will be initially
immune from any regressions by definition, (as long as compilation
doesn't break).

I'll see what I can do as far as at least doing compilation testing on
the three platforms of interest.

-Carl

-- 
carl.d.worth at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20111020/58d21d4c/attachment.pgp>