{"thread":{"id":"62016","subject":"RFE: Document \"edit\" in \"git restore --patch\"","startedAt":"2024-08-28T13:12:40Z","lastAt":"2024-08-28T13:12:40Z","messageCount":1,"participants":["Pierre Ossman"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"501762","messageId":"fddbaeb1-d9eb-4494-b196-94fd4b666471@cendio.se","threadId":"62016","inReplyTo":null,"subject":"RFE: Document \"edit\" in \"git restore --patch\"","fromName":"Pierre Ossman","fromEmail":"ossman@cendio.se","sentAt":"2024-08-28T13:02:55Z","receivedAt":"2024-08-28T13:12:40Z","isPatch":false,"sender":{"key":"ossman@cendio.se","avatar":"https://gravatar.com/avatar/d72603ba4ea49f4dd970131b7944709d2c353664d7d389e2264caa6cc8eb618c?d=mp&s=160"},"body":"Hi,\n\n\"git restore --patch\" is a very nice tool to clean up temporary gunk \nfrom your working directory. It has an \"edit\" mode, for more complex \nchunks. But it's confusing how it works, and that confusion is not \nclearly documented.\n\nWhat it seems to do is apply the edited diff *in reverse* to the working \ncopy. Technically understandable. But still annoying, and a bit of a \nbrain-teaser, although manageable as long as you are aware of it.\n\nI think it would be helpful if this is more clearly mentioned in the \ndocumentation for \"git restore\".\n\nRegards,\n-- \nPierre Ossman           Software Development\nCendio AB               https://cendio.com\nTeknikringen 8          https://twitter.com/ThinLinc\n583 30 Linköping        https://facebook.com/ThinLinc\nPhone: +46-13-214600\n\nA: Because it messes up the order in which people normally read text.\nQ: Why is top-posting such a bad thing?\n"}]}