On Sat, Jun 13, 2009 at 00:29, Markus Heidelberg<markus.heidelberg@xxxxxx> wrote: > Creating a patch series didn't work, because the SHA1 list was > interpreted in the wrong order. > > Signed-off-by: Markus Heidelberg <markus.heidelberg@xxxxxx> > --- I think they are generated in apply order as should be. As example, from git repo we have the following revisions: GIT 1.6.3 t4029: use sh instead of bash t4200: convert sed expression which operates on non-text file to perl t4200: remove two unnecessary lines Now if I select the 4 revisions and use "Save patch..." I have 0001-t4200-remove-two-unnecessary-lines.patch 0002-t4200-convert-sed-expression-which-operates-on-non.patch 0003-t4029-use-sh-instead-of-bash.patch 0004-GIT-1.6.3.patch That is correct because if I go to apply the patches I have to apply in the reverse cronological order, from the oldest to the newest. -- 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