----- Original Message -----
> I don't understand the benefit of adding a new command "mark" rather
> than continuing to use "good", "bad", plus new commands "unfixed" and
> "fixed".  Does this solve any problems?

I think it could be interesting to allow arbitrary words here. For example, I 
recently walked through history to find a performance regression, it would have 
been natural to use slow/fast instead of bad/good (bad/good would actually do 
the job, but slightly less naturally). One can look for a change which is 
neither a fix nor a bug (e.g. when did command foo start behaving like that? 
when did we start using such or such feature in the code).

I wouldn't fight for it, but I think it makes sense.

Matthieu Moy
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to