Re: packages: areca-cli/areca-cli.spec (NEW) - new; seems redistributable
On 07/03/2012 11:16 PM, glen wrote: Author: glen Date: Tue Jul 3 20:16:47 2012 GMT Module: packages Tag: HEAD Log message: - new; seems redistributable Files affected: packages/areca-cli: areca-cli.spec (NONE - 1.1) (NEW) Diffs: Index: packages/areca-cli/areca-cli.spec diff -u /dev/null packages/areca-cli/areca-cli.spec:1.1 --- /dev/null Tue Jul 3 22:16:47 2012 +++ packages/areca-cli/areca-cli.spec Tue Jul 3 22:16:42 2012 @@ -0,0 +1,55 @@ +# $Revision$, $Date$ +Summary: Utility to control Areca SATA RAID controllers +Name: areca-cli +Version: 1.86 +Release: 1 +# http://www.areca.us/support/download/RaidCards/Documents/Manual_Spec/Downloadable_Software_Licenses.zip +# Linux Exception: redistributable if not modified +License: License for Customer Use of Areca Software can somebody read the license and check whether we can repackage and distribute it? -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Git migration: beta version
I'm sorry but this time only English version. The beta version of git setup is in place. Basic informations: 1. Access: git://git.pld-linux.org/packages/PKG ssh://g...@git.pld-linux.org/packages/PKG You can try to fetch packages and upload your changes. Don't be afraid to break something. Anny changes you will make will be overwritten during the final migration. 3. Web interface: http://git.pld-linux.org/ Displaying the list of all packages can be a little slow. So probably you want to use http://git.pld-linux.org/packages/PKG 2. Mailing list with commit notifications: t...@lists.pld.linux.org Right now two types of notifications are sent to the list: a. commits relating to single branch are grouped into one email b. every commit go to a single email. For example: http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/52.html and http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/53.html http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/54.html We need to decide which version is preferred. 3. ciabot - switched off for now 4. Updated builder.sh script: git://github.com/draenog/rpm-build-tools 5. Updated version of tool to fetch changed repositories more efficiently: git-core-slug-0.12-1. Please read man slug.py 6. Documentation: http://www.pld-linux.org/dokuwiki/howto-git http://www.pld-linux.org/dokuwiki/cvs2git Any bug reports, comments etc. more then welcome. -- Kacper ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: beta version
On Wednesday 04 of July 2012 18:39:56 Kacper Kornet wrote: I'm sorry but this time only English version. The beta version of git setup is in place. Basic informations: 1. Access: git://git.pld-linux.org/packages/PKG ssh://g...@git.pld-linux.org/packages/PKG You can try to fetch packages and upload your changes. ssh access doesn't work on port 22. on port 24 it works only for user git. what about access via custom ssh-keys? ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: beta version
On Wed, Jul 04, 2012 at 07:27:53PM +0200, Paweł Sikora wrote: On Wednesday 04 of July 2012 18:39:56 Kacper Kornet wrote: I'm sorry but this time only English version. The beta version of git setup is in place. Basic informations: 1. Access: git://git.pld-linux.org/packages/PKG ssh://g...@git.pld-linux.org/packages/PKG You can try to fetch packages and upload your changes. ssh access doesn't work on port 22. fixed on port 24 it works only for user git. Everybodu shoud use user git. what about access via custom ssh-keys? Your key should work for user git. -- Kacper ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: beta version
On Wednesday 04 of July 2012 18:39:56 Kacper Kornet wrote:
Any bug reports, comments etc. more then welcome.
1). do we really need two notifications for single event?
http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/62.html
http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/63.html
2). [x/n] naming
for consistency, the short merge description
http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/66.html
should be called a [0/n] merge foo branch and following [{1..n}/n] patches
should
be sent as a reply to the 0/n (for easier emails threading).
or... the [x/n] marking should be dropped at all.
moreover, these notifications duplicate information from 'branch master
updated' emails.
imho, too much redundant notifications around the merge event.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Git migration: beta version
On Wed, Jul 04, 2012 at 08:28:07PM +0200, Paweł Sikora wrote:
On Wednesday 04 of July 2012 18:39:56 Kacper Kornet wrote:
Any bug reports, comments etc. more then welcome.
1). do we really need two notifications for single event?
http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/62.html
http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/63.html
We have to choose one of them. All commits per branch per push in one
mail (emails without [] brackets in subject), or one commit per email
(emails with [] brackets in subjects). Right now there are two to show
possible options.
2). [x/n] naming
for consistency, the short merge description
http://lists.pld-linux.org/mailman/pipermail/test/Week-of-Mon-20120702/66.html
should be called a [0/n] merge foo branch and following [{1..n}/n]
patches should
be sent as a reply to the 0/n (for easier emails threading).
The first mail (without numbers) is a sort of description. It never
contains a diff so it has no number. It shows which numbers in sequence
(1..n)/n will be missing. I will check what can be done about threading.
or... the [x/n] marking should be dropped at all.
moreover, these notifications duplicate information from 'branch master
updated' emails.
imho, too much redundant notifications around the merge event.
As I have written above. Right now there is some redundancy to show
possible options. Depending on the choice we will make you can ignore
emails with or without [] brackets in subjects.
--
Kacper
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
