Maciej Katafiasz <[email protected]> writes:
[...] > The usual procedure to help pinpoint the specific changeset > responsible is git bisect. Since you know the approximate timeframe, > and it's only a week, it should be fast and easy to find the commit in > question, and you'll likely have the answer before anyone in the know > wakes up :). Then you can go from there and start asking pointed > questions. True enough, although in this case the exercise would have been fruitless given that the problem is with recent changes in Emacs :( I'll use git bisect next time! -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : Emacs 24.3.50.1: evil 1.0-dev, org 7.9.3e, Ma Gnus v0.6, bbdb 3.02 _______________________________________________ implementations-list mailing list [email protected] https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
