Skip to content

rn-42: mention the selection of SHA-256 as NewHash #307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 20, 2018
Merged

rn-42: mention the selection of SHA-256 as NewHash #307

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions rev_news/drafts/edition-42.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,19 @@ This edition covers what happened during the month of July 2018.

## Discussions

<!---
### General
-->

* SHA-256 has been selected as Git's next-generation hash function

[Last month's
edition](https://git.github.io/rev_news/2018/07/18/edition-41/#discussions)
discussed the state of NewHash work, i.e. the process of selecting
Git's next-generation hash function. [This discussion has
concluded](https://public-inbox.org/git/20180724190136.GA5@0f3cdde9c159/)
with the selection of SHA-256. An [update to
`hash-function-transition.txt` to change `NewHash` to
`SHA-256`](https://github.com/git/git/blob/master/Documentation/technical/hash-function-transition.txt)
is queued in the `next` branch.

<!---
### Reviews
Expand Down