On Sat, Jul 23, 2011 at 9:52 PM, Ali Bahar <ali@xxxxxxxxxxxxxxx> wrote: > Hi all, > > (yes, I _am_ aware that there is a separate git mailing list. This > seemed to be more apt for _here_, as a first attempt.) > > When I run 'git format-patch' to prepare a submission, it creates a > patch-file for every commit. While this is sometimes fine, it often > isn't: I want it to skip all the interim commits which I did during > development. There is no point in (and likely prosecutable in several > jurisdictions) submitting the interim miscellany, thereby creating > needless, non-Acked, log entries in master. > > I do have a crude work-around for this, but I prefer to find out how > everyone else tackles this. I expect that it is more a _workflow_ > issue than having to do with specifying revision ranges on the > command-line. Hi, Looks like you want to generate a single commit from multiple commits. Have a look at "git rebase --interactive". You will be able to merge multiple commits into a single commit. So the workflow would be something like a) Create a new test branch b) git rebase --interactive commit-id c) Merge commits, d) git format-patch .... HTH -- Thanks - Manish _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
