Re: Git feature request: mark a commit as minor

From: Jacob Keller <jacob.keller@gmail.com>
Date: Oct 4, 2015, 06:01 UTC
Message-ID: <CA+P7+xqS0iLmo2+nLz7PyCTP7CmxjX-VONvB+-HQX9sHEiSwAw@mail.gmail.com>
In-Reply-To: <560F794F.2010809@walltime.info>

On Fri, Oct 2, 2015 at 11:44 PM, Felipe Micaroni Lalli <micaroni@walltime.info> wrote:

Show 16 quoted lines

> 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.
>
>

I think use of git-notes is probably the best way. Not sure how/if you can implement filtering on that, but I don't personally think something like this belongs in core git.

Regards, Jake