Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
I see now that Ohloh is reading the nested commits too -- all the human contributors to Launchpad are in there. I thought I looked for them before (a while ago) and didn't find them, but either I was
... [More]
mistaken (certainly possible) or something changed at Ohloh.
In any case, you can close this out. Sorry for the noise.
Note Ohloh could hide the commits from Launchpad Patch Queue Manager if it wanted to, since PQM is just a merge bot that contributes no actual code itself. But that would just be an optimization. The main thing is that the human commits be recorded, which they are.
[Less]
Since you may not be very familiar with Bazaar:
What Bzr calls a branch is more or less what other VCS systems call a repository (confusingly, Bzr has something called a repository too, but it
... [More]
doesn't really mean what you'd expect it to mean). So when I say branch above, that's more or less what you mean when you say repository.
Regarding nested commits:
When there's a top-level containing nested (inner) commits, that means the top level committer merged the inner commits into the branch. So the real author(s) of the change are the authors of the inner commits. The entity that did the merge, thus producing the top-level commit, might be a human or might be a bot, but the point is that what they did is more bookkeeping than actual code authoring.
Nesting can go to arbitrary depth; in practice, one level of nesting is by far the most common, and I've rarely seen any branch that nests beyond two levels.
[Less]
Discussion moved to Help forum:
https://www.ohloh.net/forums/10/topics/4354
Hi, Ohloh currently has two projects where there should really be one. I'm talking about the producingoss project -- there is also a producingoss_translation project, but it should just be merged into
... [More]
the producingoss project, because it's the same overall project, and anyway the translators sometimes help maintain the English original.
Is it possible to do this merge while preserving all tags and other metadata, and perhaps leaving a redirect?
Thank you, -Karl Fogel (manager of the project)
[Less]