That's my point. You wouldn't use "Fixes: 123" if it doesn't actually fix bug 123. However, what if there's a case like I said, where a bug is fixed across multiple commits. If you're using the "Fixes" tag, then technically you should only be tagging the last commit that finally fixes the bug, in which case all the other commits are left unmarked and are lost in the repository. With just a "Bug" tag, it indicates that the commit is related to the bug.
My reasoning has to do with the motivation behind why we tag commits. Maybe I'm wrong, but the reason we tag commits with bug numbers is so that, in the future, if one wants to find the commit(s) that fixed a certain bug, they can do a quick grep search on the commit log and find the relevant commits. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Wed, Jan 23, 2013 at 1:04 PM, Tim Landscheidt <t...@tim-landscheidt.de>wrote: > Tyler Romeo <tylerro...@gmail.com> wrote: > > > I would advise against doing anything with the word "Fix" in it, because > a > > commit does not necessarily fix a bug. It's possible that a fix for a bug > > spans multiple commits, depending on the scope of the bug. When you do > just > > "Bug", all it implies is that you can see that bug report for related > > information and discussion on the commit. > > > [...] > > Then why would you use "Fixes: 123" if the commit doesn't > actually fix bug #123? > > Tim > > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
