Re: Git migration: next step

2012-04-10 Thread Przemo Firszt
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

Re: Git migration: next step

2012-04-10 Thread 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

Re: Git migration: next step

2012-04-10 Thread Kacper Kornet
On Tue, Apr 10, 2012 at 04:37:37PM +0200, Jakub Bogusz wrote: As of commit logs sent to the list - package (repo) name should be added by commit log generator. If you mean mails sent after any push to the git central repository, then it is the case. In the current setup subject line looks like:

Re: Git migration: next step

2012-04-05 Thread Przemo Firszt
Dnia 3 Kwietnia 2012, 6:34 pm, Wt, Kacper Kornet napisał(a): I think all necessary pieces of code for git migration are ready. The test setup on carme has been working for some time. So if you want to check how your favourite package would like after migration please see:

Re: Git migration: next step

2012-04-05 Thread Michael Shigorin
On Thu, Apr 05, 2012 at 09:00:34AM +0100, Przemo Firszt wrote: Are we going to use git tag to mark a new version of the software or version of the spec or both? JFYI, ALT Linux uses both -- with tags being convenient to prepare the tarball for the build system. See also gear* and girar* if

Re: Git migration: next step

2012-04-05 Thread Jakub Bogusz
On Thu, Apr 05, 2012 at 09:00:34AM +0100, Przemo Firszt wrote: Dnia 3 Kwietnia 2012, 6:34 pm, Wt, Kacper Kornet napisał(a): I think all necessary pieces of code for git migration are ready. The test setup on carme has been working for some time. So if you want to check how your

Re: Git migration: next step

2012-04-05 Thread Kacper Kornet
On Tue, Apr 03, 2012 at 08:04:27PM +0200, Arkadiusz Miśkiewicz wrote: On Tuesday 03 of April 2012, Kacper Kornet wrote: Is cvsadmin job for git described anywhere? http://sitaramc.github.com/gitolite/admin.html But I will prepare small description on our wiki. How I (as user) can change my

Re: Git migration: next step

2012-04-05 Thread Kacper Kornet
On Tue, Apr 03, 2012 at 08:32:43PM +0200, Paweł Sikora wrote: On Tuesday 03 of April 2012 19:34:10 Kacper Kornet wrote: So there are following questions: B. Is there anything more that should be done before D day? do we need an extra 'Changed files:' section in git changelog? It is only

Re: Git migration: next step

2012-04-05 Thread Elan Ruusamäe
On 05/04/12 18:01, Jakub Bogusz wrote: Are we going to use git tag to mark a new version of the software or version of the spec or both? NVR tags should be done automatically like in CVS. i would expect here a bit change with the tag transforming as . was illegal in cvs, but valid in

Git migration: next step

2012-04-03 Thread Kacper Kornet
I think all necessary pieces of code for git migration are ready. The test setup on carme has been working for some time. So if you want to check how your favourite package would like after migration please see: git://carme.pld-linux.org/packages/pkg Also some documentation has been written: