fsck: don't ignore broken reflog entries
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | fsck_handle_reflog_sha1(): new functionbuiltin/ | +15 | 3 replies | |
| 2/2 | fsck: report errors if reflog entries point at invalid objectsbuiltin/ | +9 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] fsck: don't ignore broken reflog entries
Previously, if a reflog entry's old or new SHA-1 was not resolvable to an object, that SHA-1 was silently ignored. Instead, report such cases as errors.
This patch series is also available from my GitHub account [1], branch "fsck-reflog-entries".
Michael
[1] https://github.com/mhagger/git
Michael Haggerty (2):
fsck_handle_reflog_sha1(): new function
fsck: report errors if reflog entries point at invalid objects
builtin/fsck.c | 34 ++++++++++++++++++++-------------- 1 file changed, 20 insertions(+), 14 deletions(-)
Signature · 1 line
2.1.4