ebiederm@xxxxxxxxxxxx (Eric W. Biederman) writes: > Importing a quilt patch series into git is not very difficult > but parsing the patch descriptions and all of the other > minutia take a bit of effort to get right, so this automates it. > > Since git and quilt complement each other it makes sense > to make it easy to go back and forth between the two. > > If a patch is encountered that it cannot derive the author > from the user is asked. What's the expected workflow for you to work on a 1300 patch series you get from Andrew in the next installment to deal with 88 unattributed patches? Answer the question 88 times and make sure you get the answers right every time? Or abort and hand-edit them to help mailinfo to notice the correct attribution and re-run? I know I am guilty of suggesting "going interactive", but I have a feeling that having an optional file that maps patch-name to author might be easier to work with. If the old patches are recycled in the updated -mm set, you probably can reuse the mapping for them, adding entries for newly introduced "unnamed" patches as needed. - : 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