This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients alexis, brian.curtin, eric.araujo, jackjansen, jaraco, kristjan.jonsson, loewis, mark.dickinson, mhammond, python-dev, sable, santoso.wijaya, sbt, tarek, tim.golden
Date 2012-05-17.10:26:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to <[email protected]>
Content
> That sounds reasonable.  So, can't we come up with a diff that does  
> both?  The base revision sounds like a completely necessary piece of  
> info.

I believe there is a bug report against Mercurial to include the base
revision even in git-style diffs, not sure what the status is. git itself
includes the base revision in its diffs; I believe that Mercurial didn't
dare to use the same syntax since the Mercurial hash wouldn't be a valid
git hash.
History
Date User Action Args
2012-05-17 10:26:12loewissetrecipients: + loewis, mhammond, jackjansen, mark.dickinson, jaraco, kristjan.jonsson, sable, tim.golden, tarek, eric.araujo, brian.curtin, santoso.wijaya, alexis, python-dev, sbt
2012-05-17 10:26:11loewislinkissue13210 messages
2012-05-17 10:26:11loewiscreate