{"thread":{"id":"43436","subject":"git-am vs. git-applymbox","startedAt":"2006-11-05T12:10:28Z","lastAt":"2006-11-05T12:10:28Z","messageCount":1,"participants":["Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"294781","messageId":"eikkaq$au7$1@sea.gmane.org","threadId":"43436","inReplyTo":null,"subject":"git-am vs. git-applymbox","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-11-05T12:10:28Z","receivedAt":"2006-11-05T12:10:28Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"git-applymbox - Apply a series of patches in a mailbox\ngit-am        - Apply a series of patches in a mailbox\n\nWhat are the differences between thos two commands, UI-wise and capability\n(feature) wise? Which one should I use? Which one do _you_ use?\n\n\nAnd why git has yet another set of commands which do the same (well,\ngit-annotate vs. git-blame \"war\" was won by git-blame, and git-pickaxe was\nborn).\n\nBy the way, could we standarize somewhat short options for git commands,\nlike -q for quiet, -v for verbose, -i for interactive, -S for pickaxe\n(search in diff), -n for some kind of no-op/do nothing (e.g. --no-commit),\n-f for force, -l for list, -k for skip errors/keep working even in the case\nof errors? It would be nice to have this in Documentation/API somewhere...\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n\n"}]}