Hi All,
I too have been wondering how to learn how to best submit patches.
Very good discussion.
I have noticed that Airodump-ng on Atheros (Meraki mini) does not dump
real-time data to the serial port, but DOES dump real-time data to an
ssh-ethernet connection?? I am begining to make sen
Brian J. Murrell wrote:
> It would be great to see this come to a conclusion as I have submitted a
> number of patches over the last few weeks which seem to have gone
> uncommitted.
>
> Like other submitters have pointed out, I'm left in the dark as to
> whether it's just a time issue or whether
On Tue, 2008-06-24 at 09:45 +0200, Gregers Petersen wrote:
> The original thought behind the present model for submission of patches
> was based on the existing procedure for kernel patch submission - it
> looked like a model which worked, and by implementing it OpenWrt would
> "teach" people a ski
On Tue, 24 Jun 2008, RB wrote:
> > How would it look if OpenWrt tried to write into each of the package
> > make files who's maintaining them - something like this:
>
>
> I think that could work. AFAICT it still doesn't cover updates to
> trunk and its packages, but it's a start in the directio
> How would it look if OpenWrt tried to write into each of the package
> make files who's maintaining them - something like this:
I think that could work. AFAICT it still doesn't cover updates to
trunk and its packages, but it's a start in the direction of helping
focus updates for at least par
RB wrote:
>> It would be really good to extend the list of package maintainers, then
>> patches for packages could be send directly to the maintainer - or?
> As long as those package maintainers are reasonably responsive and
> have commit access. It would also need to be very clear who each
> p
> The original thought behind the present model for submission of patches
> was based on the existing procedure for kernel patch submission - it
> looked like a model which worked, and by implementing it OpenWrt would
> "teach" people a skill which could be needed later on.
I don't disagree, bu
The original thought behind the present model for submission of patches
was based on the existing procedure for kernel patch submission - it
looked like a model which worked, and by implementing it OpenWrt would
"teach" people a skill which could be needed later on.
The suggestions which have com
> "Johannes" == Johannes Ballé <[EMAIL PROTECTED]> writes:
Hi,
Johannes> On Monday 23 June 2008 12:23:45 Acinonyx wrote:
>> This surely helps the developers keep track of the submitted
>> patches but I think it makes it more time consuming to apply them
>> than emailed patches.
Johanne
On Monday 23 June 2008 12:23:45 Acinonyx wrote:
> > From my perspective, using the ticket system would be best. Then I could
> > submit my patch and forget about it afterwards, because I would be
> > notified by mail when someone made changes to the ticket.
>
> This surely helps the developers keep
On Mon, Jun 23, 2008 at 01:23:45PM +0300, Acinonyx wrote:
> Monday 23 June 2008 12:19:44 ??/?? Johannes Ball?? :
> > From my perspective, using the ticket system would be best. Then I could
> > submit my patch and forget about it afterwards, because I would be notified
> > by m
Στις Monday 23 June 2008 12:19:44 ο/η Johannes Ballé έγραψε:
> From my perspective, using the ticket system would be best. Then I could
> submit my patch and forget about it afterwards, because I would be notified
> by mail when someone made changes to the ticket.
>
This surely helps the developer
(0)419812371
-
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Johannes Ballé
Sent: Monday, 23 June 2008 7:20 PM
To: OpenWrt Development List
Subject: Re: [OpenWrt-Devel] How to submit patches to OpenWRT
On Sunday 22 June 2008
On Sunday 22 June 2008 00:06:47 RB wrote:
> 1. Non-developers submitting patches would be required to
> additionally submit a ticket for its inclusion; this gets greater
> visibility but somewhat sidesteps the whole community review bit that
> emailing the list has.
>
> 2. One of the developers c
> about this), and the developer-group would be really happy to listen to
> ideas, suggestions and practical solutions.
Although we can make suggestions we think might work, it really comes
down to what works best for the core developers (other than ignoring
input... ;) ).
Off the top of my head I
Dear All
Johannes Ballé wrote:
> It would probably already help if we could get some faint idea of how the
> devs
> manage incoming patches. Perhaps one or two additional sentences on
> https://dev.openwrt.org/wiki/SubmittingPatches would suffice.
>
>
Just to make it clear - these comments a
BTW, sorry for posting to the wrong thread. I need to switch to a different
mail agent.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Dear devs,
on Fri Jun 13 21:57:24 CEST 2008, Conrad Hirano wrote:
> Sorry, I didn't mean to offend or insult you and the other developers.
> I realize you all have lives and are busy, and I sincerely appreciate
> the time and effort you have all spent in developing OpenWRT. It's
> just a bit
18 matches
Mail list logo
