From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Martine Lenders <mlenders@riot-os.org>
Cc: authmillenon@riot-os.org, git@vger.kernel.org,
John Keeping <john@keeping.me.uk>
Subject: Re: Feature request: Configurable prefixes for git commit --fixup and --squash
Date: Thu, 03 Mar 2016 18:09:14 +0100 [thread overview]
Message-ID: <vpqvb53ij45.fsf@anie.imag.fr> (raw)
In-Reply-To: <CALHmdRwZCb7LnQcKkdy-wNx5Ree+FcMPz2ykqVnTTq_SPDR_HA@mail.gmail.com> (Martine Lenders's message of "Thu, 3 Mar 2016 17:48:18 +0100")
Martine Lenders <mlenders@riot-os.org> 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/
next prev parent reply other threads:[~2016-03-03 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 12:47 Feature request: Configurable prefixes for git commit --fixup and --squash Martine Lenders
2016-03-03 13:21 ` John Keeping
2016-03-03 13:58 ` Matthieu Moy
2016-03-03 14:38 ` Martine Lenders
2016-03-03 14:52 ` Matthieu Moy
2016-03-03 14:33 ` Martine Lenders
2016-03-03 14:44 ` John Keeping
2016-03-03 15:59 ` Matthieu Moy
2016-03-03 16:48 ` Martine Lenders
2016-03-03 17:09 ` Matthieu Moy [this message]
2016-03-03 17:23 ` Junio C Hamano
2016-03-03 17:34 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqvb53ij45.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=authmillenon@riot-os.org \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=mlenders@riot-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.