Sorry, there is no (recent) GIT history.  I announced here when I started
the "new" GIT repo that I would be using git-rebase.  I'm still doing that.
This is what made most sense while doing constant rebasing of several patch
series preparing them for upstream submission.  Now that tracehook et al
are all merged in upstream, it would not be such a hassle to maintain the
single utrace branch with fine-grained GIT history again.

What we have right now is just using GIT to hold the queue of "whole"
patches as they would be merged upstream.  Before the code is merged,
the upstream folks won't want to see any intermediate history.  They
just want to review the final "(almost) ready for prime time" versions.

I think that quite soon we will converge on the remaining API details (see
ref count thread) and have it ready to submit.  When it's merged in an
upstream GIT branch, then follow-on changes will be individual GIT commits
in branch that gets merged back in upstream, as other subsystems use.


Thanks,
Roland

  • Git log Srikar Dronamraju
    • Re: Git log Roland McGrath

Reply via email to