-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Perhaps signing merge commits is good enough. It wouldn't require new
contributors to do something more and it will be easier to keep track of the
public keys for a small group of people.
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1
iQJRBAEBC
On 05/05/2016 15:16, Bert Vermeulen wrote:
> The patch made sure the ncursesw library was not selected to save space,
> but that library doesn't exist in this distribution at all.
are you sure that ncursesw is not inside any of the feeds either ?
John
>
> Signed-off-by: Bert Vermeulen
On Fri, 6 May 2016, Kus wrote:
Daniel, I like what you said. I hinted something like that in the original
message.
I don't like the idea of making changes to history after it is published.
Personally, I don't care about commit pollution but if the team thinks it is
important, then we should
On 05/06/2016 05:54 PM, Dave Taht wrote:
On Fri, May 6, 2016 at 4:00 PM, Ben Greear wrote:
On 05/06/2016 12:05 PM, David Lang wrote:
On Fri, 6 May 2016, Ben Greear wrote:
On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I am interested in feedback on the testi
On Fri, May 6, 2016 at 4:00 PM, Ben Greear wrote:
> On 05/06/2016 12:05 PM, David Lang wrote:
>>
>> On Fri, 6 May 2016, Ben Greear wrote:
>>
>>> On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
> I am interested in feedback on the testing output. My goal
On the signature agree
On 16-05-06 08:26 PM, David Lang wrote:
> On Fri, 6 May 2016, Daniel Dickinson wrote:
>
>
> This gets back to the question about what we are trying to achieve by
> signing the commits.
>
> If the purpose is to track who put what into the central tree, then
> having the me
On 16-05-06 08:28 PM, Kus wrote:
> Daniel, I like what you said. I hinted something like that in the original
> message.
Er, sorry which part - I think you mean about fast-forward only and not
the ideal world where everything is always tested no matter who it's from?
Regards,
Daniel
>
> I don
On Fri, May 6, 2016 at 4:00 PM, Ben Greear wrote:
> On 05/06/2016 12:05 PM, David Lang wrote:
>>
>> On Fri, 6 May 2016, Ben Greear wrote:
>>
>>> On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
> I am interested in feedback on the testing output. My goal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Daniel, I like what you said. I hinted something like that in the original
message.
I don't like the idea of making changes to history after it is published.
Personally, I don't care about commit pollution but if the team thinks it is
important,
On Fri, 6 May 2016, Daniel Dickinson wrote:
Hi David,
One thing your suggestion does though, is mean that the initial commits
are not created on the master branch (for which there are few
committers), so the idea that signing all commits shouldn't be an issue
because there are only a few specia
On 05/06/2016 12:05 PM, David Lang wrote:
On Fri, 6 May 2016, Ben Greear wrote:
On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I am interested in feedback on the testing output. My goal is to add a
few more different hardware configurations and then do nightly (or
Hi David,
One thing your suggestion does though, is mean that the initial commits
are not created on the master branch (for which there are few
committers), so the idea that signing all commits shouldn't be an issue
because there are only a few special souls who create commits is not
actually the
On 05/06/2016 12:26 PM, David Lang wrote:
On Fri, 6 May 2016, Ben Greear wrote:
On 05/06/2016 12:05 PM, David Lang wrote:
On Fri, 6 May 2016, Ben Greear wrote:
On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I am interested in feedback on the testing output. My g
On Fri, 6 May 2016, Ben Greear wrote:
On 05/06/2016 12:05 PM, David Lang wrote:
On Fri, 6 May 2016, Ben Greear wrote:
On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I am interested in feedback on the testing output. My goal is to add a
few more different hardware
On 05/06/2016 12:05 PM, David Lang wrote:
On Fri, 6 May 2016, Ben Greear wrote:
On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I am interested in feedback on the testing output. My goal is to add a
few more different hardware configurations and then do nightly (or
On 16-05-06 02:58 PM, David Lang wrote:
> On Fri, 6 May 2016, Kus wrote:
>
>>
>> I'd argue such a barrier is OK if we want to quickly increase the size
>> of the team of people with commit access. I think we're
>> underestimating our contributors here. I agree that we shouldn't have
>> unnecessary
On Fri, 6 May 2016, Ben Greear wrote:
On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I am interested in feedback on the testing output. My goal is to add a
few more different hardware configurations and then do nightly (or at
least weekly) tests.
So that is showin
On Fri, 6 May 2016, Kus wrote:
Regarding signing commits with GPG key, it would be nice to recommend it but
making it a requirement sounds like a barrier.
I'd argue such a barrier is OK if we want to quickly increase the size of the
team of people with commit access. I think we're underestima
On 16-05-05 04:16 AM, Michal Hrusecky wrote:
> David Lang - 18:20 4.05.16 wrote:
>> Debian has ...
>
> Just for the sake of discussion and inspiration, how openSUSE does it's
> rolling
> release. We have OBS, which is server software, connected to multiple
> builders.
[snip]
Thank you David a
On 05/06/2016 10:20 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I am interested in feedback on the testing output. My goal is to add a
few more different hardware configurations and then do nightly (or at
least weekly) tests.
So that is showing up to 10s of *seconds* of latency, rig
Also on the topic of bug reports, having some mechanism for users to
report 'I also have this problem, but have nothing new to add'
launchpad-esque mechanism for finding how many people the bug affects
without spamming the tracker with 'me too', would be good.
This helps with
a) higher numbers o
+1
Fernando
On 6 May 2016 at 12:05, Daniel Dickinson wrote:
> Hi all,
>
> I have noticed that some of the policies of this project are already
> veering towards a brand of technical elitism that I feel is completely
> contrary to the stated goal of having a stronger community.
>
> A strong commu
Here is an automated test result that I have added to our wifi
testing gear.
The basic idea is that we associate more and more stations and run throughput
tests at each iteration. Goal is to test stability, capacity, and see how
performance
varies as more stations are associated.
AP is Ventana
On 16-05-06 11:55 AM, Kus wrote:
>
>> Regarding signing commits with GPG key, it would be nice to recommend it but
>> making it a requirement sounds like a barrier.
>
> I'd argue such a barrier is OK if we want to quickly increase the size of the
> team of people with commit access. I think we'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> Regarding signing commits with GPG key, it would be nice to recommend it but
> making it a requirement sounds like a barrier.
I'd argue such a barrier is OK if we want to quickly increase the size of the
team of people with commit access. I thi
On Fri, 2016-05-06 at 11:48 -0400, Daniel Curran-Dickinson wrote:
> > As I said, the issue is not with 'only good bug reports', it's with 'we
> > can ensure only good bug reports by making it a pain to report bugs at all'.
>
> I'd also like to point out that if the approach is being taken on the
>
> As I said, the issue is not with 'only good bug reports', it's with 'we
> can ensure only good bug reports by making it a pain to report bugs at all'.
I'd also like to point out that if the approach is being taken on the
assumption that on technically advanced people write good reports, then
I'd
On 16-05-06 11:29 AM, David Woodhouse wrote:
> On Fri, 2016-05-06 at 11:05 -0400, Daniel Dickinson wrote:
>>
>> Technical elitism tends give a 'you're not good enough / you don't think
>> like us, go away' feel to a community. The 'we won't event look at your
>> bug report if it doesn't meet the s
Hi,
I just signed up here.
On 05/06/2016 05:03 PM, Jo-Philipp Wich wrote:
> Hi,
>
>> I am concerned that git signing gives little, if any value, while making
>> it harder to contribute (and making it easier to contribute is one of
>> the *stated* goals of LEDE) and is another example of a tenden
On Fri, 2016-05-06 at 11:05 -0400, Daniel Dickinson wrote:
>
> Technical elitism tends give a 'you're not good enough / you don't think
> like us, go away' feel to a community. The 'we won't event look at your
> bug report if it doesn't meet the special format we came up with that no
> one else u
Hi all,
I have noticed that some of the policies of this project are already
veering towards a brand of technical elitism that I feel is completely
contrary to the stated goal of having a stronger community.
A strong community welcomes 'outsiders' and noobs and helps them find
their place in the
Hi,
> I am concerned that git signing gives little, if any value, while making
> it harder to contribute (and making it easier to contribute is one of
> the *stated* goals of LEDE) and is another example of a tendency toward
> a particular brand of technical elitism that will kill this project if
I am concerned that git signing gives little, if any value, while making
it harder to contribute (and making it easier to contribute is one of
the *stated* goals of LEDE) and is another example of a tendency toward
a particular brand of technical elitism that will kill this project if
not nipped in
I'm an outsider, have nothing to do with OpenWrt developement but
still work on few projects which depend on OpenWrt as awesome project
that enables us to do our projects (wifi mesh networking) but also do
professional jobs for clients using OpenWrt as embedded os for lots of
different applications
Hi all,
I know other community members of complained about the lack of
information about the reasons for the fork (they and I don't think
LEDE's official announcement really provides enough information to
really understand the situation) and I especially do badly in a vacuum -
I tend to strain to
On 5/5/2016 7:40 AM, Felix Fietkau wrote:
Many of the changes that we previously tried to introduce were often
squashed by internal disagreements. Resulting discussions often turned
toxic quickly and led to nothing being done to address the issues.
Setting up the LEDE project was our way of cre
On 16-05-05 03:22 PM, mbm wrote:
> On 5/5/2016 7:40 AM, Felix Fietkau wrote:
>> Many of the changes that we previously tried to introduce were often
>> squashed by internal disagreements. Resulting discussions often turned
>> toxic quickly and led to nothing being done to address the issues.
>> Set
On Thu, 5 May 2016 19:56:04 +0200
Matthias Schiffer wrote:
> As I understand git's commit signing feature, the signature is
> something that is added by the committer, not the author. This means:
>
> - the format-patch/send-email format does *not* contain a signature
> - reviewed-by etc. can be
Might I submit that my impression is that Kaloz (at least) holds
infrastructure hostage to maintain control, and that the fundamental
problem here is that OpenWrt is *not* democratic and ignores what people
who were ones visibly working on openwrt want and overrides their wishes
because he/they has
From: Daniel Dickinson
Branding: Rename openwrt to lede where appropriate
(although probably some unnecessary changes were made due
to not looking all that closely and doing a relatively mindless
(but not automatic) search and replace).
Probably this commit is incomplete and also has some things
>On 2016-05-05 20:22, mbm wrote:
>> On 5/5/2016 7:40 AM, Felix Fietkau wrote:
>>> Many of the changes that we previously tried to introduce were often
>>> squashed by internal disagreements. Resulting discussions often turned
>>> toxic quickly and led to nothing being done to address the issues.
mbm schrieb am 05.05.2016 um 21:22:
> On 5/5/2016 7:40 AM, Felix Fietkau wrote:
>> Many of the changes that we previously tried to introduce were often
>> squashed by internal disagreements. Resulting discussions often turned
>> toxic quickly and led to nothing being done to address the issues.
Might I submit that my impression is that Kaloz (at least) holds
infrastructure hostage to maintain control, and that the fundamental
problem here is that OpenWrt is *not* democratic and ignores what people
who were ones visibly working on openwrt want and overrides their wishes
because he/they has
On Fri, 6 May 2016 10:14:04 +0100
Felix Fietkau wrote:
> During the rsync operation, package lists could go out of sync with
> the .ipk files, or a mirror might be pulling an incomplete list of
> files. To reduce the chance of this happening, let rsync put all
> updated files into place at the e
So far fixtrx was calculating checksum over amount of data matching
partition erase size. It was mostly a workaround of checksum problem
after changing anything in initial TRX content (e.g. formatting JFFS2).
Its main purpose was to make bootloader accept modified TRX. This didn't
provide much prot
Hi Daniel,
thanks for hosting the mirrors!
ideally you poll the rsync server every 3 hours, that roughly
corresponds to the current duration of the buildbot cycles.
We'll see how well this works out in the future and adjust accordingly,
if needed.
~ Jo
_
the reboot was not meant to be hostile or disruptive to OpenWrt. we are
just code nerds and messed up the politics of the launch at some places,
which in itself shows one of the reasons that motivated the reboot. the
whole idea is to give up our control over parts of the politics and
attract a new
On Fri, 2016-05-06 at 12:41 +0300, Daniel Petre wrote:
> Hello, so per jow's last night's info i have rsynced the downloads part
> from LEDE to the RCS&RDS ( www.rcs-rds.ro ) mirroring server:
>
> http://mirrors.linux.ro/lede/
>
> Two more questions please:
>
> 1. How often can we rsync?
> 2. D
Hello, so per jow's last night's info i have rsynced the downloads part
from LEDE to the RCS&RDS ( www.rcs-rds.ro ) mirroring server:
http://mirrors.linux.ro/lede/
Two more questions please:
1. How often can we rsync?
2. Do you need anything else rsynced?
Thanks!
P.S. Contact e-mail for the
During the rsync operation, package lists could go out of sync with the
.ipk files, or a mirror might be pulling an incomplete list of files.
To reduce the chance of this happening, let rsync put all updated files
into place at the end of the transfer
Signed-off-by: Felix Fietkau
---
master/phas
Dear Jo and folks steering the ship,
Regarding Linux Foundations' offering, kindly take into consideration
their recent action: http://mjg59.dreamwidth.org/39546.html
Now upon looking at the grants page below:
https://www.coreinfrastructure.org/grants
One worries about terms like: "Under th
On 6 May 2016 at 03:53, Luka Perkov wrote:
>>On 2016-05-05 20:22, mbm wrote:
>>> On 5/5/2016 7:40 AM, Felix Fietkau wrote:
Many of the changes that we previously tried to introduce were often
squashed by internal disagreements. Resulting discussions often turned
toxic quickly and le
Hi,
Taking this from lede-adm to lede-dev where I'm allowed to post...
On 06/05/16 02:33, Alexander Couzens wrote:
>> +== What devices does LEDE targets?
>> +
>> +LEDE mainly targets embedded devices capable of running Linux.
> I agree.
>
>> In
>> most cases wireless routers. This has not chang
53 matches
Mail list logo
