Unfortunately, your patch blocks selecting and copying the result text.
I don't know why all the previous commits are still showing here even after being merged.
A combination of practices and events led to that;
you are working on your master branch instead of a fresh branch for the issue; see Contributing, search in page, and read the sections that mention the word branch,
you did not keep your repository up to date with this repository; which is made more difficult by your using master branch,
your previous pull request was merged by me using the rebase method, so that the merge commit could be avoided (a merge commit makes history noisy and git bisect more difficult),
another patch was committed to master here by me,
Consequence is that you have a different view of history in your repository than in this repository.
Thanks. Reviewed.
Method;
git fetch chimosky
git checkout af8a888
sugar-activity
Unfortunately, your patch blocks selecting and copying the result text.
A combination of practices and events led to that;
master
branch instead of a fresh branch for the issue; see Contributing, search in page, and read the sections that mention the word branch,master
branch,git bisect
more difficult),master
here by me,Consequence is that you have a different view of history in your repository than in this repository.
You can fix it like this;
Assuming that origin is the
git remote
name for your repository, and sugarlabs is thegit remote
name for this repository.For your confidence, I have tested this with your GitHub repository; the result looks like this;
Looking at the log for this clone shows the history has been normalised; the duplicate commits reduced, and the new commit placed at the end.