{"thread":{"id":"1540","subject":"Re: [RFC] Patches exchange is bad?","startedAt":"2005-08-16T22:09:22Z","lastAt":"2005-08-16T22:45:21Z","messageCount":2,"participants":["Marco Costalba","Daniel Barkalow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"7391","messageId":"20050816220923.42545.qmail@web26301.mail.ukl.yahoo.com","threadId":"1540","inReplyTo":null,"subject":"Re: [RFC] Patches exchange is bad?","fromName":"Marco Costalba","fromEmail":"mcostalba@yahoo.it","sentAt":"2005-08-16T22:09:22Z","receivedAt":"2005-08-16T22:09:22Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"Martin Langhoff wrote:\n\n>>From what I understand, you'll want the StGIT infrastructure. If you\n>use git/cogito, there is an underlying  assumption that you'll want\n>all the patches merged across, and a simple cg-update will bring in\n>all the pending stuff.\n>\n\nMy concerns are both metodologicals and practical:\n\n1) Method: To use the 'free patching workflow' on git is something foreseen in\ngit design, something coherent with the fork + develop + merge cycle that it\nseems, at least to me, THE way git is meant to be used. Or it is stretching \nthe possibility of the tool to something technically allowed but not suggested.\n\n2) Practical: The round trip git-format-patch + git-applymbox is the logical and\nnatural way to reach this goal or, also in this case, I intend to stretch some tools, \ndesigned for one thing, for something else?\n\n\nAbout StGIT, I agree it is the right tool, designed for this kind of problems. But,\nperaphs because I don't know it very much, I still can't figure out how to integrate \nStGit in a git GUI, like qgit is, so to have an unified and friendly view of a git \narchive and a patches stack.\n\n\nMarco\n\n\n\n__________________________________________________\nDo You Yahoo!?\nTired of spam?  Yahoo! Mail has the best spam protection around \nhttp://mail.yahoo.com \n"},{"id":"7393","messageId":"Pine.LNX.4.63.0508161824140.23242@iabervon.org","threadId":"1540","inReplyTo":"20050816220923.42545.qmail@web26301.mail.ukl.yahoo.com","subject":"Re: [RFC] Patches exchange is bad?","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2005-08-16T22:45:21Z","receivedAt":"2005-08-16T22:45:21Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Tue, 16 Aug 2005, Marco Costalba wrote:\n\n> Martin Langhoff wrote:\n>\n> >>From what I understand, you'll want the StGIT infrastructure. If you\n> >use git/cogito, there is an underlying  assumption that you'll want\n> >all the patches merged across, and a simple cg-update will bring in\n> >all the pending stuff.\n> >\n>\n> My concerns are both metodologicals and practical:\n>\n> 1) Method: To use the 'free patching workflow' on git is something foreseen in\n> git design, something coherent with the fork + develop + merge cycle that it\n> seems, at least to me, THE way git is meant to be used. Or it is stretching\n> the possibility of the tool to something technically allowed but not suggested.\n\nPatches are definitely meant to be part of how git is used; they are the\nprimary way of getting clean history out of messy history (that is, saving\na content change while discarding some history that isn't applicable).\nThere's relatively little support in git itself, but that's because the\npoint is to go outside the system's tracking. There have been various\ndiscussions of more explicit support, and nobody's been able to come up\nwith a need.\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\nI'd guess that git-diff-tree + git-apply (without the rest of the\nscripting) would be more effective when you're not doing anything with the\nintermediate files, since it saves doing a bunch of formatting and\nparsing.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}