-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: |> Same reason... you're peeling off the patches that fix those issues. | | Hmm, when I pulled some of the changes last week, I could build | just fine. Now when I go back to the same changes, they need | fixes they didn't need before ?
Yeah because what those patches are patching has changed. |> | Furthermore, the dates look wrong. E.g., ar6k-essid-one-and-32.patch |> | was added around September 16, but commit |> | d41035e9ef253ddd2e9d2c59b550fdfab1719d0a says November 1. |> |> Same reason... | | So git doesn't keep the timestamps with the changes ? That's | weird. How does one set the timestamps then ? I shouldn't be The timestamps are reset when I rebase them. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkOTDgACgkQOjLpvpq7dMrO1ACeNDjHRaNb+ncJRIv9WPwR2wEO 5ZYAn3FjbDkuyZpg7t0vuUepXPQphyig =0ug2 -----END PGP SIGNATURE-----
