Flags

8 things noticed while rendering the history

r1870400018:1316 (deleted, was .commit_msg.txt)

• overlap r1870400018:3977 and r1870400018:4053 concurrently named r1870400018:1327+416..417
• overlap r1870400018:3977 and r1870400018:4053 concurrently named r1870400018:3972+0..28
• swallowed r1870400018:3977 edited r1870400018:1316 (deleted, was .commit_msg.txt) while r1870400018:4256 concurrently deleted it, so the edit is present in the log and absent from the tree
• swallowed r1870400018:4025 edited r1870400018:1316 (deleted, was .commit_msg.txt) while r1870400018:4256 concurrently deleted it, so the edit is present in the log and absent from the tree
• swallowed r1870400018:4031 edited r1870400018:1316 (deleted, was .commit_msg.txt) while r1870400018:4256 concurrently deleted it, so the edit is present in the log and absent from the tree
• swallowed r1870400018:4053 edited r1870400018:1316 (deleted, was .commit_msg.txt) while r1870400018:4034 concurrently deleted it, so the edit is present in the log and absent from the tree
• swallowed r1870400018:4130 edited r1870400018:1316 (deleted, was .commit_msg.txt) while r1870400018:4034 concurrently deleted it, so the edit is present in the log and absent from the tree
• yielded r1870400018:3977 was one of 2 concurrent edits over overlapping content; r1870400018:4053 was highest in op order and prevailed, so this edit is in the log and not in the file