Skip to content

Conversation

kevinwallace
Copy link

This makes gitbrute convenient to use on a series of commits after rebasing.
Otherwise, date information for those commits is completely destroyed.

This makes gitbrute convenient to use on a series of commits after rebasing.
Otherwise, date information for those commits is completely destroyed.
cemeyer added a commit to cemeyer/gitbrutec that referenced this pull request May 30, 2019
Design inspired heavily by https://github.com/bradfitz/gitbrute .

'git hash-object ...' suggestion from rdebath in
bradfitz#7 .

Like bradfitz#5 , this program walks the
commit and authorship dates backward, rather than the current date.

Like bradfitz#8 , we have the same
problem.  Fortunately, current dates are 10 digits long; it would take about
2^58 iterations to actually come up with a shorter time_t in decimal; we're
way too CPU limited to realistically be brute forcing hashes with 58 bits of
prefix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant