On 12 February 2014 03:57, Sébastien Luttringer wrote:
> On 11/02/2014 14:39, Bartłomiej Piotrowski wrote:
>> On 02/11/2014 02:37 AM, Sébastien Luttringer wrote:
>>> - Send a message on aur-gene...@al.org
>>> - Write some lines in the AUR package comments
>>> - Open a BR for inclusion
>>> - Push h
On 11/02/2014 14:39, Bartłomiej Piotrowski wrote:
> On 02/11/2014 02:37 AM, Sébastien Luttringer wrote:
>> - Send a message on aur-gene...@al.org
>> - Write some lines in the AUR package comments
>> - Open a BR for inclusion
>> - Push his new package to community
This is a short list of well known
On 02/11/2014 02:37 AM, Sébastien Luttringer wrote:
> - Send a message on aur-gene...@al.org
> - Write some lines in the AUR package comments
I usually write a message directly to package maintainer, asking if he
see any problems deterring the package from inclusion. I really don't
see why I shoul
Hi,
Most of the time, when a TU is working on adding a new package to
community, he could:
- Send a message on aur-gene...@al.org
- Write some lines in the AUR package comments
- Open a BR for inclusion
- Push his new package to community.
This let him time to carefully:
- Test his modification
-
4 matches
Mail list logo