Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#2315 closed Enhancement (worksforme)

Commit messages lack context

Reported by: jch Owned by:
Priority: Low Milestone: None Set
Component: Wiki Version: 1.73
Severity: Minor Keywords:
Cc:

Description

A lot of the commit messages in transmission svn lack context, making it difficult to work out what the change is about without generating a diff. Here's an example:

(trunk gtk) remove some unused code

which is pretty cool, but it would be better if there were a hint about what unused code was removed. Similarly, there's

(trunk libT) possible fix for #2238 as suggested by kjg

which is completely useless unless I go and check what's in #2238.

Folks, as a personal favour to me, could you please get into the habit of giving context in commit messages? Say,

remove unused code in torrent parsing

or

possible fix for web interface freeze (#2238)

Thanks,

--Juliusz

Change History (2)

comment:1 Changed 12 years ago by livings124

  • Component changed from Transmission to Wiki
  • Resolution set to worksforme
  • Status changed from new to closed

We do try to give context, but sometimes linking to the ticket should be sufficient. We'll try to keep this in mind.

Resolving as "worksforme" just because none of the choices seem too applicable.

comment:2 Changed 12 years ago by charles

I mostly agree with livings124's comment, but I'd add that

(trunk libT) possible fix for #2238 as suggested by kjg

is *not* completely useless because if you view it via trac, such as from <http://trac.transmissionbt.com/log/>, it automatically marks up #2238 to be a link to #2238.

Note: See TracTickets for help on using tickets.