Open
Bug 1119643
Opened 11 years ago
Updated 2 years ago
Likely bug in pushlog handling of 0 sized database file
Categories
(Developer Services :: Mercurial: Pushlog, defect)
Developer Services
Mercurial: Pushlog
Tracking
(Not tracked)
NEW
People
(Reporter: gps, Unassigned)
References
Details
Attachments
(1 obsolete file)
Apparently a 0 size pushlog2.db file may cause pushlog to get in a funky state. I *think* the repro is:
1) touch pushlog2.db
2) Attempt to pull from that repo (with the pushlog extension installed)
Updated•2 years ago
|
Attachment #9387630 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•