{"thread":{"id":"25949","subject":"Presenting git timetracker tool, asking asking git notes merge","startedAt":"2010-12-04T07:49:16Z","lastAt":"2010-12-04T07:49:16Z","messageCount":1,"participants":["Eduardo Robles Elvira"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"157299","messageId":"AANLkTi=XOF83Ch8aU0Nj+KDUjvobM_7cT08bDT3k9bNr@mail.gmail.com","threadId":"25949","inReplyTo":null,"subject":"Presenting git timetracker tool, asking asking git notes merge","fromName":"Eduardo Robles Elvira","fromEmail":"edulix@wadobo.com","sentAt":"2010-12-04T07:49:16Z","receivedAt":"2010-12-04T07:49:16Z","isPatch":false,"sender":{"key":"edulix@wadobo.com","avatar":null},"body":"Hello everyone!\n\nI'm glad to present you a new git tool I've been working on together\nwith Daniel (danigm), the new git timetrack comand, part of the\ndistributed time tracker project [1]. It allows you to track the time\nspent in commits done to a git repository. I want to thanks for the\nhelp to the people in #git-devel IRC Channel, without their help this\nwould have been much more difficult to develop.\n\nGit timetracker uses Git notes to add Time-spent annotations to\ncommits. It actually requires git-next because it makes use of git\nnotes merge. Git timetracker is really easy to use, a small example is\nshown in the wiki [1]. As a tip, notice that git timetrack --summary\naccept the same options as git log, so for example you can do a git\ntimetrack --summary --since=1week dir/file.c .\n\nWhy did we develop timetracker? We are creating a small software\ncompany and we needed to do (rough) estimations of the time the\ndevelopment in the projects we work on will take, so we thought that\nthe first thing we need to do that is to have some real information\nabout time spent in those projects.\n\nWhen the user does a git push, the timetracker notes are pushed,\nbecause git timetrack --init adds a push=... line to the remote in the\nconfig files. When it does git pull, it also pulls notes because of a\nfetch=..., and it merges those notes in refs/notes/merge with an\npost-merge hook. That solution is suboptimal, because for example when\ndoing git pull --rebase that doesn't work, and the user needs to do\nmanually a git timetrack --merge. Can't we add an option to git pull\nto merge the fetched notes? For me, as a git notes user, it would be\ngreat if I had something like\nfetch=refs/notes/timetracker:refs/notes/timetracker and\nnotes-automerge=refs/notes/timetracker in my remote, and then doing a\ngit pull automatically calls to git notes merge.\n\nRegards,\n   Eduardo\n--\n[1] http://wadobo.com/trac/dtt\n"}]}