Patrick Steinhardt <ps@xxxxxx> writes: In the subject: s/leaging/leaking > When computing rename conflicts in our recursive merge algorithm we set > up `struct rename_conflict_info`s to track that information. We never > free those data structures though and thus leak memory. > > We need to be a bit more careful here though because the same rename > conflict info can be assigned to multiple structures. Accomodate for Nit: s/Accomodate/Accommodate [snip]
Attachment:
signature.asc
Description: PGP signature
