[PATCH 0/3] update sha1dc from PR #36

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This hopefully fixes the Solaris SPARC issue & doesn't cause
regressions elsewhere, e.g. on Cygwin. Adam, it would be great if you
could test that platform.

I've already confirmed with Michael Kebe + another SPARC user
(CosmicDJ on Freenode #Solaris) that it works on Solaris SPARC. The
question is whether it breaks anything else.

Per the upstream pull request:
https://github.com/cr-marcstevens/sha1collisiondetection/pull/36

Marc would (understandably) like some wider testing of this before
merging it into the upstream project.

WRT the submodule URL & branch changing: I have no idea how
git-submodule handles this in the general case, but it Just Works with
GitHub because it allows fetching arbitrary SHA1s that any ref
(including pull req refs) point to. So on top of pu just doing "git
submodule update" works to update to the new copy.

Junio C Hamano (1):
  sha1collisiondetection: automatically enable when submodule is
    populated

Ævar Arnfjörð Bjarmason (2):
  sha1dc: update from my PR #36
  sha1dc: optionally use sha1collisiondetection as a submodule

 .gitmodules            |  4 +++
 Makefile               | 16 ++++++++++
 hash.h                 |  4 +++
 sha1collisiondetection |  1 +
 sha1dc/sha1.c          | 80 ++++++++++++++++++++++++++++++++++++++------------
 5 files changed, 86 insertions(+), 19 deletions(-)
 create mode 100644 .gitmodules
 create mode 160000 sha1collisiondetection

-- 
2.13.1.611.g7e3b11ae1




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux