From: Javier Domingo Cansino <javierdo1@gmail.com>
To: Andrius Bentkus <andrius.bentkus@gmail.com>
Cc: Stefan Beller <stefanbeller@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Idea, Transparent commits, easier "code style" commits
Date: Sun, 6 Jul 2014 15:37:00 +0200 [thread overview]
Message-ID: <CALZVapnofGirkPBFcgNp4-GZnrNAi3ZXDZA1LM-y3_LYQHksXA@mail.gmail.com> (raw)
In-Reply-To: <CAAwotL3vtkjVO5Zqz+w_gNSS0OAovUfukK8=-Df9K4ZybzNh0A@mail.gmail.com>
> They just have to look into the commit message and look for
> "#codestylefix" or whatever other string.
In many projects I have seen, they have a format for commits, such as
"docs: Add support for XXX", "formatting: Space before parethesis and
after comas", "tests: ...." and so on.
Maybe, being able to specify a RegExp would be the way to go, so that
git blame did actually ignore those commits.
prev parent reply other threads:[~2014-07-06 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 13:12 Idea, Transparent commits, easier "code style" commits Andrius Bentkus
2014-07-04 15:26 ` Stefan Beller
2014-07-06 11:44 ` Andrius Bentkus
2014-07-06 13:37 ` Javier Domingo Cansino [this message]
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=CALZVapnofGirkPBFcgNp4-GZnrNAi3ZXDZA1LM-y3_LYQHksXA@mail.gmail.com \
--to=javierdo1@gmail.com \
--cc=andrius.bentkus@gmail.com \
--cc=git@vger.kernel.org \
--cc=stefanbeller@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).