Hi git list, I think it would be useful if git-quiltimport.sh recognized a flag to tell it to add a "QuiltFilename:" or "PatchFilename:" trailer to each imported commit, which would show the filename of the patch that that commit was imported from. This would make it much easier (reliably possible, in fact) to match up imported commits with their original patch; this is something I frequently want to do, since the original patches might have additional information associated with them that is not imported into git. (For example, a comment in the quilt "series" file, or version control history of the patch if it is kept in version control). If such a flag and trailer were added, I think another useful addition could be made to git format-patch: a flag to read the "PatchFilename: " trailer and create the patch with that name. This would make it possible to use git format-patch to regenerate the entire quilt patch series without changing the filename or performing other unnecessary churn. This is desirable because git tools like interactive rebase are very powerful for manipulating a patch series, and it would be nice to be able to use those without unnecessarily renaming all the patches. (Of course, it would be even nicer to be able to just maintain these patches in git... but sometimes you really do need them as a patch series, in which case this ability would come in handy) (And of course, format-patch still causes some other churn, like adding the "From HASH DATE" line at the top of the patch and updating the version number at the bottom, so it would be nice if there were flags to stop it from adding those as well) I can write patches to add all these features, but I thought it was best to ask first, since adding a new pseudo-header/trailer might be a radical step. I could alternatively do all of this with some local bash scripts wrapping quiltimport and format-patch, but I think these features might be useful to others too. Thanks! -- 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