Git migration: next step

[Jakub Bogusz]

On Tue, Apr 10, 2012 at 09:41:47AM +0100, Przemo Firszt wrote:
> 
> Dnia 5 Kwietnia 2012, 4:01 pm, Cz, Jakub Bogusz napisał(a):
> > On Thu, Apr 05, 2012 at 09:00:34AM +0100, Przemo Firszt wrote:
> >>
> [..]
> >> Can we agree a naming convention? Something like:
> >> "package-name: description" (it's similar to kernel patches)
> >> i.e. "xorg-driver-input-wacom: up to 14.0.0" or
> >> "xorg-driver-input-wacom: fix invalid BuildReq"?
> >
> > I don't find "package-name: " prefix useful, as there (AFAIK) will be
> > one package per repository.
> [..]
> In the repository it's useless, but on the list, I think, it's quite
> important: compare [1] and [2]. The subject of [1] is useless on the list.

Ah, you mean commit names in patches sent to the list, not committed.
Then package name is useful of course.

As of commit logs sent to the list - package (repo) name should be added
by commit log generator.


BTW - how changelog entries are made of git commit messages (wrt. "short"
and "long" part, to be concrete)?
I forgot about this difference between cvs and git.


-- 
Jakub Bogusz    http://qboosh.pl/