Daniel Barkalow wrote: >>2) Practical: The round trip git-format-patch + git-applymbox is the logical >>and >>natural way to reach this goal or, also in this case, I intend to stretch >>some tools, >>designed for one thing, for something else? > > >I'd guess that git-diff-tree + git-apply (without the rest of the >scripting) would be more effective when you're not doing anything with the >intermediate files, since it saves doing a bunch of formatting and >parsing. > > It would be surely better, but I need to import also the original subject and description. I can use git-diff-tree --pretty -p for the patch creation, but this format is not compatible with git-apply* scripts, and the git command git-apply does not import subject + description info.
Of course I can feed proper subject and description to git-commit but I would like to find something less intrusive as possible, ie. one command for patch export, one command for patch import. Thanks Marco __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
