Martine Lenders <mlenders@xxxxxxxxxxx> writes: >> [ Please, don't top-post on this list ] ... and as much as possible keep the "XYZ wrote:" line so that we know who wrote what ;-). I wrote: >> I wish I could write commit messages like >> >> fixup! deadbeef: fix typo (foo -> bar) >> >> So that the commit message contains both the instruction for "rebase >> --autosquash" and a quick explanation of what the commit is doing (as >> usual commit messages). >> >> AFAIK, it's not possible currently but shouldn't be hard to implement. > > I would love that, too :-). This differs however from the original > intent of my feature request. So maybe we finish this thread (since my > John's proposal is 100% sufficient for me in that regard) and open a > new one? How are the procedures for this on this list? We don't have "procedure" for feature requests. It happens often that someone dreams aloud like I did above, and it's OK as long as "it shouldn't be hard to implement" is understood as "one day I should do it" and not "hey, you lazy devs, why don't you code that for me?" ;-). But in general, people get more interested when a proposal has a patch attached. I've added the idea here: https://git.wiki.kernel.org/index.php/SmallProjectsIdeas (except I already changed my mind in the syntax) I may get some students to work on this in May, or do it myself one day. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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