{"thread":{"id":"1553","subject":"Re: [RFC] Patches exchange is bad?","startedAt":"2005-08-17T08:27:09Z","lastAt":"2005-08-17T09:07:19Z","messageCount":2,"participants":["Marco Costalba","Martin Langhoff"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"7434","messageId":"20050817082709.28135.qmail@web26301.mail.ukl.yahoo.com","threadId":"1553","inReplyTo":null,"subject":"Re: [RFC] Patches exchange is bad?","fromName":"Marco Costalba","fromEmail":"mcostalba@yahoo.it","sentAt":"2005-08-17T08:27:09Z","receivedAt":"2005-08-17T08:27:09Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"Daniel Barkalow wrote:\n\n>>2) Practical: The round trip git-format-patch + git-applymbox is the logical and\n>>natural way to reach this goal or, also in this case, I intend to stretch some tools,\n>>designed for one thing, for something else?\n>\n>\n>I'd guess that git-diff-tree + git-apply (without the rest of the\n>scripting) would be more effective when you're not doing anything with the\n>intermediate files, since it saves doing a bunch of formatting and\n>parsing.\n>\n>\nIt would be surely better, but I need to import also the original subject and\ndescription. I can use git-diff-tree --pretty -p for the patch creation, but this\nformat is not compatible with git-apply* scripts, and the git command git-apply does\nnot import subject + description info.\n\nOf course I can feed proper subject and description to git-commit but I would like \nto find something less intrusive as possible, ie. one command for patch export, one \ncommand for patch import.\n\nThanks\nMarco\n\n\n__________________________________________________\nDo You Yahoo!?\nTired of spam?  Yahoo! Mail has the best spam protection around \nhttp://mail.yahoo.com \n"},{"id":"7436","messageId":"46a038f90508170207578b1c0@mail.gmail.com","threadId":"1553","inReplyTo":"20050817082709.28135.qmail@web26301.mail.ukl.yahoo.com","subject":"Re: [RFC] Patches exchange is bad?","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2005-08-17T09:07:19Z","receivedAt":"2005-08-17T09:07:19Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 8/17/05, Marco Costalba <mcostalba@yahoo.it> wrote:\n> Of course I can feed proper subject and description to git-commit but I would like\n> to find something less intrusive\n\nI don't know if it helps, but I think that StGIT is what you are\nlooking for, not only because you have more tools to deal with\npatches, but also because patches that are in the 'stack' are actually\nreally malleable. You can edit and reedit the patch w its commit msg\nand all, commit it to the stack, and reedit it again later. It only\nbecomes immutable when you commit to the underlying git repo.\n\ncheers,\n\n\nmartin\n"}]}