On 17.03.2010, at 09:28, Pieter de Bie wrote: > On Wed, Mar 17, 2010 at 8:41 AM, Uli Kusterer <[email protected]> wrote: >> On 17.03.2010, at 04:29, Stephen Bannasch wrote: >>> I often put small bits of code in commit messages. >> >> I'm wondering if you are putting documentation in your commit messages here? > > I don't think it's GitX's task to tell people how they should document > their project. Using blame as a documentation tool generally works > great for me, as you can easily get all relevant commit messages for a > specific range of code. > > Telling people to use the first line in the commit message as a > subject is one thing, telling them to separate documentation from > commit messages is something else.
Agreed, we should not tell anyone what to do. However, spending extra work on a feature that is used in 1 out of several thousand commit messages, and that no other VCS client I've used has, sounds a bit like we're losing sight of the 80/20 rule. A monospaced font with the ability to resize the window lets people edit/view ASCII art as needed, even if the field soft-wraps to its width. But I don't think I should discuss this to death, so I'll shut up now. Whoever implements it in the end gets to make the decision. I can always change it in my fork if whatever solution you find causes me problems :-) Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://groups.yahoo.com/group/mac-gui-dev/
