{"thread":{"id":"23219","subject":"git-am: Please don't be in \"some state\" when it fails early","startedAt":"2010-03-29T00:14:24Z","lastAt":"2010-03-29T00:14:24Z","messageCount":1,"participants":["Ulrik Sverdrup"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"138037","messageId":"a1b6cb1b1003281714u50dbcc2bh58c38b50a7b837cd@mail.gmail.com","threadId":"23219","inReplyTo":null,"subject":"git-am: Please don't be in \"some state\" when it fails early","fromName":"Ulrik Sverdrup","fromEmail":"ulrik.sverdrup@gmail.com","sentAt":"2010-03-29T00:14:24Z","receivedAt":"2010-03-29T00:14:24Z","isPatch":false,"sender":{"key":"ulrik.sverdrup@gmail.com","avatar":null},"body":"If git am fails early, before even trying to apply the first patch, it\nwould be great if am did not leave some state that has to be manually\ncleaned up (git am --abort). Even if I have a small 'AM' marker in my\nprompt, it is often missed. And why write state files to .git/ at all,\nif all it did was to tell me that the index is dirty?\n\nThis fixes an inconvenience, and I don't have to wonder (look up)\nevery time if git am --abort will delete all the WIP I had in the way\nor not.\n\nUlrik\n"}]}