Carl Worth <cworth@xxxxxxxxxx> writes: > Another option would be to just emit RFC2822 messages unless the user > passes an explicit option to format-patch (such as --mbox, which would > be implied by --stdout). Then git would generate legitimate (unqoted) > messages and legitimate (quoted) mbox files. > > I'd leave it to you to decide whether the --mbox option should be on by > default or phased in with a warning or whatever. > > What do you think? It sounds like that one good way to transition is to phase in --mbox as an optional feature and at a revision bump later make that the default (which would mean that we might need a --not-a-mbox option). I haven't thought things through though... 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