From: Felipe Micaroni Lalli <micaroni@walltime.info>
To: Mikael Magnusson <mikachu@gmail.com>,
Jacob Keller <jacob.keller@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Git feature request: mark a commit as minor
Date: Sat, 3 Oct 2015 03:44:31 -0300 [thread overview]
Message-ID: <560F794F.2010809@walltime.info> (raw)
In-Reply-To: <CAHYJk3Qb89YhVJoOpBLYMoNJX5GvVHnJhf41Gdbtypcp+Yq96g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
Thank you Jacob.
Actually we already use the keyword MINOR for that, exactly as you said.
The suggestion was made because I think it is a common behavior and it
would be nice to be a meta info to standardize this (today each team
adopt a different pattern for that - you used "TRIVIAL" e.g.). Nice
things could be done with this meta-info. It could be totally ignored
(current git operation) or it could be used to filter, to sort, to group
commits, to show the log pretty etc.
> The issue is that not everyone considers these changes as "minor".
I understand this issue, I know it is subjective. But if someone don't
want to make the distinction just don't use the argument --hide-minor
for example.
On 03/10/2015 03:17, Mikael Magnusson wrote:
> On Sat, Oct 3, 2015 at 8:11 AM, Jacob Keller <jacob.keller@gmail.com> wrote:
>> On Fri, Oct 2, 2015 at 2:38 PM, Felipe Micaroni Lalli
>> <micaroni@walltime.info> wrote:
>>> A minor change (also called "cosmetic") usually is a typo fix, doc
>>> improvement, a little code refactoring that don't change the behavior etc.
>>>
>>> In Wikipedia we can mark an edition as "minor".
>>>
>>> It would be nice to have an argument like "--minor" in git-commit to
>>> mark the commit as minor. Also, filter in git-log (like --hide-minor) to
>>> hide the minor changes. The git-log could be optimized to show minor
>>> commits more discreetly.
>>>
>>>
>>
>> This should just be part of the commit message log, generally projects
>> use something like TRIVIAL in the patch subject or similar. You could
>> also standardize for your project(s) what would be considered a minor
>> change. The issue is that not everyone considers these changes as
>> "minor". You should be able to use a combination of the --grep option
>> in log to search for all commits who don't contain that string in the
>> right format.
>
> Could also be a good use for notes, since you might want to add this
> markup after the fact.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-03 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 21:38 Git feature request: mark a commit as minor Felipe Micaroni Lalli
2015-10-03 6:11 ` Jacob Keller
2015-10-03 6:17 ` Mikael Magnusson
2015-10-03 6:44 ` Felipe Micaroni Lalli [this message]
2015-10-04 6:01 ` Jacob Keller
2015-10-03 18:12 ` Fredrik Gustafsson
2015-10-03 19:52 ` Felipe Micaroni Lalli
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=560F794F.2010809@walltime.info \
--to=micaroni@walltime.info \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=mikachu@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).