Re: [O] Erroneous "No such file or directory" with babel and remote dir

[Loris Bennett]

Achim Gratz <address@hidden> writes:

> Loris Bennett writes:
>>> Can you try to bisect and find the bad commit (or a set of 
>>> suspicious ones)?
>>
>> 552b0edb254a104e441e28f3a942dc6005e97f87 is the first bad commit
>> commit 552b0edb254a104e441e28f3a942dc6005e97f87
>> Author: Bastien Guerry <address@hidden>
>> Date:   Sat Mar 17 15:44:41 2012 +0100
>
> This is not the commit you're looking for...
>
> Please "skip" these commits after starting the bisect by doing
>
> git bisect skip 7e903acccd..df82832fb7
>
> If the offending change is inside that range we can still deal with it
> later.
>
>
> Regards,
> Achim.

OK.  I don't really get what is going on here, as this is my first
attempt at bisecting.  The bad commit does seem to be among those
skipped:

$ git bisect bad
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
095e5786761d4edd51dfdfc9a69cd22b942096fa
b0e24a2b5e3ce872e9eb43462f03edf616438f57
cdd9e2b91a7b9257e4f94e0aacc8e470ac1c951a
73cbeabe1b457da1364547d7f2d89db889bec926
9382faf5927f84a2c496ae677d99b64517abeeb2
05847efd4ace13fda174c2f1d8dc354eb217ea35
c63275ca8ea46e0e96ab7ed70efe6bb937c39b29
82019bc7c7a786303e82cfa5891193acb3754606
b2913c9227504ffd31d616482d258f5b10f821fb
49dd6de08384f913f014ac06c24da4ff08ccdb6a
dab84afa7592e842ae866881c532cd60944bb0da
552b0edb254a104e441e28f3a942dc6005e97f87
b32d2f737d567222bdbdf742329b9a34d0dd069a
a1a01224d4c1f76761e3562c54020c04bfd3ac9b
ecd0562c5f6e69ce0e4546d9f64d8e89eda8eef1
5ed0384e51449e6462eed3a6ff4ecba6a6f52790
6bcba149195c2c281eefc3065dabe2ec1fdea687
4e5c24ea81c6758241a828e28ea44b75d36115e3
856f5c27fb11a1f034c80fc29c39f211434fc650
06b94ca884733eaefb0ec868d641da78ed536ceb
df82832fb7525e5d57f1e968334e1057329e95f2
6c911234ac66d62d99cb0c996dc10c938b2b3679
We cannot bisect more!


-- 
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin         Email address@hidden