<div class="gmail_quote">On Fri, Dec 3, 2010 at 06:45, Thomas Arendsen Hein <span dir="ltr"><<a href="mailto:thomas@intevation.de">thomas@intevation.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
mercurial/subrepo.py uses "cmd += ['--date', ...", but --date was<br>
added in Git 1.7.0, which is newer than the current version in<br>
Debian stable (1.5.6.5).<br></blockquote><div><br></div><div>I have tested with git 1.6 (and now again with 1.5.6.5), and my git correctly logs the date when passed. The date passed by mercurial and the default date in the tests are different, and the commit hashes would change if it didn't recognize the --date option.</div>
<div><br></div><div>My results are from building git at specified versions, could Debian be doing something funny?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This breaks test-subrepo-git.t (and of course the actual<br>
functionality, but since this is new, I do not yet miss it :))<br></blockquote><div><br></div><div>Unfortunately I have no idea how to make the tests pass with git older than 1.7. The tests pass with the newest version of git, but git's output changes too much before 1.7. Almost all commands are told to be quiet, but older versions have different ideas of what quiet means, and still some double quotes were changed to single quotes, etc.</div>
<div><br></div><div>The tests functionally work with 1.6 (and 1.5.6.5), and major versions before 1.6 expect commands to be 'git-commit' instead of 'git commit' and should fail verbosely (although not descriptively).</div>
<div><br></div><div>-Eric</div></div>