<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Can't edit file on samba shares" href="https://bugs.documentfoundation.org/show_bug.cgi?id=115747#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Can't edit file on samba shares" href="https://bugs.documentfoundation.org/show_bug.cgi?id=115747">bug 115747</a> from <a class="email" href="mailto:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> Aron Budea</a> <pre>Hi, thanks for giving it a try! (In reply to Jerome from <a href="show_bug.cgi?id=115747#c6">comment #6</a>) > 1) I successfully cloned bibisect-linux-64-6.0 ( about 6GB). Seems correct so far. > 2) git latest and git oldest give errors (error: pathspec 'latest' did not > match any file(s) known to git) There's definitely an "oldest" tag that marks the first commit of the repo (the first commit of 6.0), but indeed the latest commit isn't tagged. You can checkout the oldest commit like this: git checkout oldest And the latest (which checks out master branch): git checkout master > 3) git log displays only 3 commits, which looks strange given the 6GB of the > cloning output: There's a lot more than that (almost 8k commits), but 'git log' only shows as many as can fit on a screen, you can scroll by hitting space. But let's forget that, let me sketch down the steps: 1. Check out master to make sure you're at the latest commit with: git checkout master 2. Check the commit hash (the one on top that start with "commit") with: git log -1 3. Start bibisecting with: git bisect start <latest commit hash> oldest 4. There will be 13 or so steps (each step halves the commit range). At each step repeat your bug repro steps, and type the command as follows: - if the bug occurs: git bisect bad - if there's no issue: git bisect good - if the build doesn't start: git bisect skip 5. When you arrive at a single commit, post the hash "source sha" here. If anything is still unclear, ask away.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>