From: Holger Schurig <holgerschurig@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] fixup! command: add hmac sum supportfor md5, sha1, sha224, sha256, sha384, sha512
Date: Thu, 2 Apr 2015 09:11:33 +0200 [thread overview]
Message-ID: <CAOpc7mHqV-qLrpK2Kaus3q3shPTnjWeCw4wozA6b4b6s5=Sy-A@mail.gmail.com> (raw)
In-Reply-To: <20150329110427.24206daaf84c5fff0d668ae2@gmail.com>
Antony,
that git has such a function doesn't mean that it is usable in any git
project. I too, like Jean-Christophe, that a style issue shouldn't be
named as a fix,
You could always do "git commit --amend" to change the message so that
it actually describes what happens.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-04-02 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 16:23 Antony Pavlov
2015-03-28 20:07 ` Jean-Christophe PLAGNIOL-VILLARD
2015-03-29 8:04 ` Antony Pavlov
2015-04-02 7:11 ` Holger Schurig [this message]
2015-04-02 7:27 ` Antony Pavlov
2015-04-03 6:15 ` Sascha Hauer
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='CAOpc7mHqV-qLrpK2Kaus3q3shPTnjWeCw4wozA6b4b6s5=Sy-A@mail.gmail.com' \
--to=holgerschurig@gmail.com \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox