hal: Branch 'origin' - 3 commits

[David Zeuthen]

On Mon, 2006-09-25 at 09:23 +0200, Danny Kukawka wrote:
> On Monday 25 September 2006 00:01, David Zeuthen wrote:
> > On Sat, 2006-09-23 at 20:37 -0700, Artem Kachitchkine wrote:
> > > Uh, I didn't do it...
> >
> > That's just git acting up I think or so someone with more knowledge told
> > me once. Does anyone (Kay?) know how to fix this? We don't really need
> > to track the origin branch; all we need is 'master' and the various
> > branches off releases...
> 
> I have no idea, how to fix it, but there are also some other issues which 
> sucks on (current) git (config):

I certainly agree the commit-to-mail script we're using can be improved
and I'm hoping to get someone to help me us here. I don't have the time
right now to look into this, if you want feel free to tinker around with
it.

> * see commit mail from David: [1], which contains a already commited patch 
> from Artem. This make the patch/change nearly unreadable in the mail and you 
> can't use the mail as patch for e.g. a diff for a released package.

Right. gitk, git-log and git-short-log still works though.

> * the subject of the commit mails say nothing about the change/commit. Only 
> all the time this "hal: Branch 'master'" stuff. I would like to see the same 
> as in CVS/SVN before. The name of the branch and the first line of the _real_ 
> commit as mail subject.

Yea, that clearly sucks. We can do much better.

     David