What do you think about using something like Jira for project
management(which is free for open source projects)? I know it was used by
cyanogenmod with decent success. One other potential advantage would be the
possibility of CI testing being tied in more closely.
On Mon, Oct 12, 2015 at 1:46 AM,
On 12/10/2015 08:38, Steven Barth wrote:
> Let's face it though: the current workflow wrt. core patches is crappy.
>
> 1. Go to patchwork, see if there is a patch
> 2. If you want to comment, switch to mail client, find thread, write reply.
> 3. If you want to commit: download patch, go to comma
Let's face it though: the current workflow wrt. core patches is crappy.
1. Go to patchwork, see if there is a patch
2. If you want to comment, switch to mail client, find thread, write reply.
3. If you want to commit: download patch, go to command line, see if it applies
4. Then manually go back t
2015-10-11 14:16 GMT-07:00 Attila Lendvai :
>> Just my 2-cents
>>
>> IF it isn't BROKENplease DON'T fix it.
>
>
> the question here is: how much time coders (maintainers, contributors,
> and users) would spare if the administration was shifted to a
> different infrastructure.
>
> i cannot grow
Sets the LEDs to boardname:color:led-name
Sets the LAN to eth0
Other corrections such as the Machine Name and HWIDs
v2 corrects the profile names in the Makefile and changes tabs to spaces
in the Makefile 'define Device/' like the other devices.
Signed-off-by: L. D. Pinney
---
target/linux/ar
Hi Nathan,
thanks for sharing your patch. I'm the author of patch #3828, but I haven't
been able to access it at:
http://patchwork.openwrt.org/patch/3828/
and I don't have a local copy of it.
So I relied on your patch and it seems to work flawlessly.
Also, you said:
The patch (#3828) works well f
> Just my 2-cents
>
> IF it isn't BROKENplease DON'T fix it.
the question here is: how much time coders (maintainers, contributors,
and users) would spare if the administration was shifted to a
different infrastructure.
i cannot grow to like git (i still prefer darcs), but github simply
prov
i got a patchwork mail[1] with the short message
"patch is superseeded" - but no further comments,
so the question is:
1) who closed the patch?
2) why is it 'superseeded', but not fixed?
bye, bastian
[1] http://patchwork.ozlabs.org/patch/528164/
___
op
* John Crispin [11.10.2015 20:40]:
> also please prefix your patches with ar71xx: and not [ar71xx]
can please somebody change the text in
https://dev.openwrt.org/wiki/SubmittingPatches
@ "13. The canonical patch format"
-> Subject: [PATCH 001/123] [section] summary phrase
i made this mistake se
Certain things are certainly broken. The body of kernel code that OpenWrt
maintains (allows to bitrot) outside the upstream kernel tree is broken.
Regarding downstream forks, would using Git also make it easier for people
like project turris to push appropriate changes back into OpenWrt proper?
Just my 2-cents
IF it isn't BROKENplease DON'T fix it.
On Sun, Oct 11, 2015 at 1:26 PM, Nemesis wrote:
> On 10/10/2015 07:45 PM, nemesis wrote:
>
> On Sat, 10 Oct 2015 00:41:24 +0300, Roman Yeryomin
> wrote:
>
> On 9 October 2015 at 21:22, Jo-Philipp Wich
> wrote:
>
> Hi.
>
> Moving
On 10/10/2015 07:45 PM, nemesis wrote:
> On Sat, 10 Oct 2015 00:41:24 +0300, Roman Yeryomin
> wrote:
>> On 9 October 2015 at 21:22, Jo-Philipp Wich wrote:
>>> Hi.
>>>
Moving to Git seemed to have lots of traction at the summit, and I'll
add my voice that this sounds like a step in the r
Sets the LEDs to boardname:color:led-name
Sets the LAN to eth0
Other corrections such as the Machine Name and HWIDs
Signed-off-by: L. D. Pinney
---
target/linux/ar71xx/base-files/etc/diag.sh| 6
--
target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
On 11 Oct 2015, at 14:48, John Crispin wrote:
patches will linger in mailing list until someone has time to look at
them. the version control system used is completely irrelevant
Which is true enough if the switch just encompasses moving to another VCS.
However, what has not been made explicit e
> On 11 Oct 2015, at 14:48, John Crispin wrote:
>
> patches will linger in mailing list until someone has time to look at
> them. the version control system used is completely irrelevant
Which is true enough if the switch just encompasses moving to another VCS.
However, what has not been made
Hi,
On 07/10/2015 17:34, Daniel Petre wrote:
> This adds support to generate images for tp-link wr841n v10 which is almost
> identical with tp-link wr841n v9 but with a faster cpu at 650 Mhz. Tested on
> a european version.
>
> Signed-off-by: Daniel Petre
>
> --- a/target/linux/ar71xx/image/M
The IRQF_DISABLED flag was removed in kernel 4.1 with commit
"genirq: Remove the deprecated 'IRQF_DISABLED' request_irq() flag entirely" [1].
Therefore the compilation of ltq-hcd and ltq-vmmc kmods fails.
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d8bf368d0631
Hello John,
On Sun, Oct 11, 2015 at 2:48 PM, John Crispin wrote:
>
> On 11/10/2015 14:09, Jan Čermák wrote:
> > Hello,
> >
> > thanks for pointing that out, Steven. Yes, this is basically the main
> > reason why
> > Bedrich opened this topic. If you need to maintain sustainable OpenWrt fork
> >
comments inline
On 10/10/2015 04:44, Riley Baird wrote:
> This patch fixes ticket #15267 by enabling power on the
> WNR2200's USB port. At present, the USB port on the WNR2200
> is non-functional due to it not receiving power.
>
> This patch defines an additional GPIO pin, but none of the
> curre
On 11/10/2015 14:09, Jan Čermák wrote:
> Hello,
>
> thanks for pointing that out, Steven. Yes, this is basically the main reason
> why
> Bedrich opened this topic. If you need to maintain sustainable OpenWrt fork
> (no
> flame please, there are some situations - like running "heavyweight" Open
Hello,
thanks for pointing that out, Steven. Yes, this is basically the main reason why
Bedrich opened this topic. If you need to maintain sustainable OpenWrt fork (no
flame please, there are some situations - like running "heavyweight" OpenWrt
fork on a device like our Turris - when it's reasonab
Am 11.10.2015 um 10:50 schrieb Arjen de Korte:
Citeren Mathias Kresin :
diff --git a/package/kernel/lantiq/ltq-hcd/src/ifxhcd.c
b/package/kernel/lantiq/ltq-hcd/src/ifxhcd.c
index be0a91d..14dc7a1 100644
--- a/package/kernel/lantiq/ltq-hcd/src/ifxhcd.c
+++ b/package/kernel/lantiq/ltq-hcd/src/ifx
Citeren Mathias Kresin :
The IRQF_DISABLED flag was removed in kernel 4.1 with commit
"genirq: Remove the deprecated 'IRQF_DISABLED' request_irq() flag
entirely" [1].
Therefore the compilation of ltq-hcd and ltq-vmmc kmods fails.
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/l
The IRQF_DISABLED flag was removed in kernel 4.1 with commit
"genirq: Remove the deprecated 'IRQF_DISABLED' request_irq() flag entirely" [1].
Therefore the compilation of ltq-hcd and ltq-vmmc kmods fails.
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d8bf368d0631
Please read our package submission guidelines here
https://github.com/openwrt/packages/blob/master/CONTRIBUTING.md
and once your submission complies, create a pull
request at: https://github.com/openwrt/packages
Cheers,
Steven
___
openwrt-devel mailing
25 matches
Mail list logo
