Aaron Bentley wrote: > Sean wrote: > >> Petr already mentioned that the data currently shown in the email >> text isn't really useful. > > In Bazaar bundles, the text of the diff is an integral part of the data. > It is used to generate the text of all the files in the revision. I thought that the diff was combined diff of changes. > Bazaar bundles were designed to be used on mailing lists. So you can > review the changes from the diff, comment on them, and if it seems > suitable, merge them. If you have only mega-diff, you can comment only on this mega-diff. It is more usefull for changes which have natural mult-commit history, to review and comment on each of commits/patches in series _separately_. >> Although that might just make the email bigger for not a lot of >> gain. > > It's my understanding that most changes discussed on lkml are provided > as a series of patches. Bazaar bundles are intended as a direct > replacement for patches in that use case. As _series_ of patches. You have git-format-patch + git-send-email to format and send them, git-am to apply them (as patches, not as branch). I was under an impression that user sees only mega-patch of all the revisions in bundle together, and rest is for machine consumption only. cg-bundle doesn't have this "mega-diff", but has shortlog (does bzr bundle has shortlog/log of changes contained therein?) and diffstat was planned. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html