On Fri, Oct 2, 2015 at 11:44 PM, Felipe Micaroni Lalli <micaroni@xxxxxxxxxxxxx> wrote: > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html