Patches in patchwork

Patches in patchwork

[Koen Kooi]

Hi,

The following patches in patchwork still have the 'new' status:

(e)glibc.inc: add minimal sane kernel versions	
  wvstreams fix	
  cacao: add missing patch	
  checksums.ini: added entry for gtksourceview2_2.6.0	
  gtksourceview: renamed the 1.x tree to gtksourceview1	
  gtksourceview2 2.6.0: new recipe for the current stable version.	
  bitbake.conf, freeze.inc: Add version lockdown implementation and use 
it by default.	
  linux: drop alix, move geodelx to 2.6.29	
  kaeilos: use include/sane-feed.inc	
  kaeilos.inc/sane-feed.inc: use spaces instead of tabs	
  kaeilos/sane-feed: remove alix, mark geodelx as i586	
  Remove alix machine, update geodelx one to use Alix settings	
  at2440evb.conf: Add AT2440EVB machine config.	
  mtools now an FSF project	
  grub: Split the grub-install script and friends into a separate package.	
  Remove unused grub-0.93.	
  python-native_2.6.1.bb: Add zlib-native to DEPENDS	
  u-boot: update git recipe with the new DaVinci EVMs	
  linux-davinci: build linux-davinci kernels for dm6446, dm6467 and 
dm355 EVMs	
  dm357-evm: add new machine definition	
  dm365-evm: add new machine definition	
  dm355-evm: add new machine definition and defconfig	
  dm6467-evm: add new machine definition and defconfig	
  dm6446-evm: rename machine from davinci-dvevm and add defconfig	
  davinci.inc: add common DaVinci machine configuration	
  x11-gpe-java-image: gdk-pixbuf	
  python-native_2.6.1.bb: Configure with --with-zlib	
  grub: split menu.lst into a separate package, grub-config.	
  grub: use ${libdir}, not /usr/lib	
  Remove unused grub-0.93.	
  at2440evb.conf: Add AT2440EVB machine config.	
  grub: allow menu.lst to be overridden using GRUB_CONFIG_PACKAGE.	
  Remove unused grub-0.93.	
  kernel.bbclass: also stage include/trace if it's available	
  kernel.bbclass: stage more include files for x86 in 2.6.27+	
  Fix staging of binutils static libraries	
  enable zlib in python-native to fix image building, cannot import 
gzip module	
  gcc_4.2.4.bb: QA Issue: No GNU_HASH in theelf binary	
  gcc_4.2.4.bb: QA Issue: No GNU_HASH in theelf binary	
  uclibc-initial: Fix FILESPATH mangling in all versions	
  dsplink: change path to the XDC tools directory	
  gcc_4.2.4.bb: QA Issue: No GNU_HASH in the elf binary	

All: please have a look at them and update the status/mail 
comments/apply/whatever.

The oldest ones are nearly a month old now...


regards,

Koen

Re: Patches in patchwork

[Dmitry Eremin-Solenikov]

Koen Kooi wrote:

> Hi,
> 
> The following patches in patchwork still have the 'new' status:
> 

What is the policy/process for gaining the ability to change/comment
other people patches in patchwork? I'd like to do some work on it
but I'd like to have ability to reflect the status of applied patches
in the patchwork.

-- 
With best wishes
Dmitry

Re: Patches in patchwork

[Philip Balister]

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

Dmitry Eremin-Solenikov wrote:
> Koen Kooi wrote:
> 
>> Hi,
>>
>> The following patches in patchwork still have the 'new' status:
>>
> 
> What is the policy/process for gaining the ability to change/comment
> other people patches in patchwork? I'd like to do some work on it
> but I'd like to have ability to reflect the status of applied patches
> in the patchwork.

I don't think you can directly comment in patchwork. If you want to 
change status you need to register. I've been changing everyone to be 
able to change patch status. Please note, if you have accents in your 
username, I cannot change your patchwork privileges.

Does this answer your question?

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

Re: Patches in patchwork

[Dmitry Eremin-Solenikov]

Philip Balister wrote:

> Dmitry Eremin-Solenikov wrote:
>> Koen Kooi wrote:
>> 
>>> Hi,
>>>
>>> The following patches in patchwork still have the 'new' status:
>>>
>>>
>> What is the policy/process for gaining the ability to change/comment
>> other people patches in patchwork? I'd like to do some work on it but
>> I'd like to have ability to reflect the status of applied patches in
>> the patchwork.
> 
> I don't think you can directly comment in patchwork. If you want to
> change status you need to register. I've been changing everyone to be
> able to change patch status. Please note, if you have accents in your
> username, I cannot change your patchwork privileges.
> 
> Does this answer your question?

Yes, thank you.

-- 
With best wishes
Dmitry