Redundant github refs with rebase

Martin Stein martin.stein at ...1...
Wed Jan 25 10:23:06 CET 2012

Thank you for your quick feedback :-)

This seems to be a good
example git branch -vva --contains
890161ff6037233a477b804eb7cc199e059a8343 || true; shows that the commit,
wich was reported twice is only contained by one branch and its remote
counterpart. I rebased it to a new driver version immediately befor i
wrote its successor.


On 01/25/2012 10:03 AM, Christian Helmuth wrote:
> Hello,
> the first response was not that satisfying, so I explained the
> behavior in more detail to the support. While doing this I was
> wondering if you may have the commit in several branches, which would
> explain what we see, but
>   for hash in 560c166f0ce5d990dff63d1c729f052b13c35b45 \
>               fe9935ccae91efd04c0f4ee5bb45160e3ec7cfb1 \
>               dee3d9374db2aa06b861d6e6e2bd882191c7dc15 \
>               0bc9f5cd41e74d901e9bbb51285affa9a1f4801f \
>               38626b02f5e7dd64cb3f1ff22d80d3373f265c85; do
>       echo $hash
>       git branch -vva --contains $hash || true;
>   done
> showed me that only 38626b02f5e7dd64cb3f1ff22d80d3373f265c85 is used.
> Greets

More information about the users mailing list