getting users involved in on-device testing

Hi, It would be nice if there was a process in place that would allow community members to easily be able to test images on devices and report the results some place. after some time thinking of different ways to do this I came up with one possible solution and wanted to know what others think abo

Re: Proposal to sign all commits

On 05/05/2016 08:42, David Lang wrote: > On Thu, 5 May 2016, John Crispin wrote: > >> On 05/05/2016 07:38, David Lang wrote: >>> On Thu, 5 May 2016, John Crispin wrote: >>> On 04/05/2016 23:38, Kus wrote: > Greetings > > I'd like to propose that all commits (at least to master)

Re: Proposal to sign all commits

On Thu, 5 May 2016, John Crispin wrote: On 05/05/2016 07:38, David Lang wrote: On Thu, 5 May 2016, John Crispin wrote: On 04/05/2016 23:38, Kus wrote: Greetings I'd like to propose that all commits (at least to master) going forward be signed with the commiter's gpg key. https://git-scm.co

Re: [LEDE-DEV] List Prefix

On 27/04/2016 10:47, John Crispin wrote: > > > On 26/04/2016 18:51, David Woodhouse wrote: >> On Tue, 2016-04-26 at 17:16 +0200, Jo-Philipp Wich wrote: >>> This is just a test, please ignore. >> >> Hm, I thought I fixed the stupid mailman default when I set up the >> list, to remove the pointle

Re: Proposal to sign all commits

On 05/05/2016 07:38, David Lang wrote: > On Thu, 5 May 2016, John Crispin wrote: > >> On 04/05/2016 23:38, Kus wrote: >>> Greetings >>> >>> I'd like to propose that all commits (at least to master) going >>> forward be signed with the commiter's gpg key. >>> >>> https://git-scm.com/book/en/v2/Gi

Re: Proposal to sign all commits

On Thu, 5 May 2016, John Crispin wrote: On 04/05/2016 23:38, Kus wrote: Greetings I'd like to propose that all commits (at least to master) going forward be signed with the commiter's gpg key. https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work Thoughts? we could do that. if you lo

Re: List subject prefix?

On Thu, 5 May 2016, John Crispin wrote: On 04/05/2016 23:31, Aaron Z wrote: On many (most?) mailing lists, there is a prefix on all subjects which has the list name (such as [OpenWRT-Devel]) Can this prefix be added for this list (or is that an option that I missed when I signed up)? Hi, it

Re: Proposal to sign all commits

On 04/05/2016 23:38, Kus wrote: > Greetings > > I'd like to propose that all commits (at least to master) going forward be > signed with the commiter's gpg key. > > https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work > > Thoughts? we could do that. if you look at the keyring.git, you

Re: List subject prefix?

On 04/05/2016 23:31, Aaron Z wrote: > On many (most?) mailing lists, there is a prefix on all subjects which > has the list name (such as [OpenWRT-Devel]) > Can this prefix be added for this list (or is that an option that I > missed when I signed up)? Hi, it was chosen not to use this prefix.

Re: [OpenWrt-Devel] Getting in touch with Felix

Hi, Even jow@openwrt and blogic@openwrt do not exist anymore as of now. Recipient address rejected: User unknown in virtual mailbox table While for example juhosg@openwrt still exists. I just hope this will not become another "ffmpeg vs libav"... Cheers, Vittorio On 05/05/2016 02:00:29 CES

Re: Wiki for LEDE Project

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I love this idea. A wiki with pages for each router :D and people who have that particular machine can come in and write about the quirks about it. It will be great! -BEGIN PGP SIGNATURE- Version: APG v1.1.1 iQJRBAEBCgA7BQJXKscxNBxLdXNoYWw

Contacting Felix

Hey, Could you let Felix know I wanted to apologize to him for getting upset previously on the openwrt list, because of situations he is obviously also frustrated with? I can't reach him because n...@openwrt.org bounces and I don't have a record of his other addresses. Regards, Daniel

Wiki for LEDE Project

Hi, Any plans to have a Wiki for LEDE, preferably using the MediaWiki software ? I personally think MediaWiki is a great software, easy to maintain and upgrade plus the fact that many people know how to write on it. Also is possible to have a clean presentation for the pages created specially for

Re: [RFC] A change to the way packages are built

On Wed, 4 May 2016, Daniel Dickinson wrote: Thoughts? The problem I expect you to run into is dependencies between packages. Yes, although I primarily thinking of it from the package failed because a package it depends on fails or has default configuration that doesn't work with the package.

Re: [RFC] A change to the way packages are built

On 16-05-04 08:38 PM, David Lang wrote: > On Wed, 4 May 2016, Daniel Dickinson wrote: > >> Hi, >> >> I wanted to know if there is any appetite for an idea I've been kicking >> around in my head for a while for package builds. >> >> Basically one builds a minimal SDK and does kind of like Debian wh

Re: [RFC] A change to the way packages are built

On Wed, 4 May 2016, Daniel Dickinson wrote: Hi, I wanted to know if there is any appetite for an idea I've been kicking around in my head for a while for package builds. Basically one builds a minimal SDK and does kind of like Debian where a git commit to a package kicks of a build of pristine

Re: project goals

On Wed, 4 May 2016, Vittorio G (VittGam) wrote: Hi, On 04/05/2016 22:30:40 CEST, Bert Vermeulen wrote: Hi all, Very happy to see this project reboot happening. An acknowledgement of the issues facing OpenWRT was long overdue. I'd like some clarity on some things that aren't explicitly menti

Re: Proposal to sign all commits

On Wed, 4 May 2016, Kus wrote: I'd like to propose that all commits (at least to master) going forward be signed with the commiter's gpg key. https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work Thoughts? Other than the possible idea that you can know if a commit was created by the

[RFC] A change to the way packages are built

Hi, I wanted to know if there is any appetite for an idea I've been kicking around in my head for a while for package builds. Basically one builds a minimal SDK and does kind of like Debian where a git commit to a package kicks of a build of pristine environment which builds only the package and

Re: [OpenWrt-Devel] Introducing the LEDE project

Sorry if this hits the list twice, I sent from the wrong email and got bounced. On 16-05-04 06:05 PM, Bob Call wrote: > On Wed, 2016-05-04 at 21:19 +0100, tapper wrote: >> On 04/05/2016 21:01, mbm wrote: >>> >> [snip] > > I'm kind of split on this issue because I run a faltering OpenWRT fork, > f

Re: List subject prefix?

+1 I'm also missing the common [TAG] for this mailing list. Thanks! On 04/05/16 23:31, Aaron Z wrote: > On many (most?) mailing lists, there is a prefix on all subjects which > has the list name (such as [OpenWRT-Devel]) > Can this prefix be added for this list (or is that an option that I > miss

Re: Introducing the LEDE project

On Wed, 2016-05-04 at 21:19 +0100, tapper wrote: > On 04/05/2016 21:01, mbm wrote: > > > > Dear OpenWrt community, > > > > It is with a great amount of surprise that, like all of you, we > > read > > about the announcement of the LEDE project yesterday, as there was > > no > > prior announcement

Re: project goals

Hi, On 04/05/2016 22:30:40 CEST, Bert Vermeulen wrote: Hi all, Very happy to see this project reboot happening. An acknowledgement of the issues facing OpenWRT was long overdue. I'd like some clarity on some things that aren't explicitly mentioned in the stated goals, however. First off, is

Re: [OpenWrt-Devel] Introducing the LEDE project

On 04/05/2016 21:01, mbm wrote: Dear OpenWrt community, It is with a great amount of surprise that, like all of you, we read about the announcement of the LEDE project yesterday, as there was no prior announcement nor clues this would happen. While we recognize the current OpenWrt project suffe

Re: Introducing the LEDE project

Dear OpenWrt community, It is with a great amount of surprise that, like all of you, we read about the announcement of the LEDE project yesterday, as there was no prior announcement nor clues this would happen. While we recognize the current OpenWrt project suffers from a number of issues ou

Re: Proposal to sign all commits

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Jo, Never done it in a real project. Signing commits should not make things any worse. The worst thing that can happen as far as I know is we are back to where we are today. Rewriting history can be a pain from what I've read. However, I think

Re: Proposal to sign all commits

Hi Kus, the idea sounds good in general but I cannot yet judge the practical implications of doing that. Here's some random question that spring to mind: - Is the signature retained in "git format-patch" output? - Does it have any negative impact on casual "cloners" ? - What happens when used ke

Proposal to sign all commits

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Greetings I'd like to propose that all commits (at least to master) going forward be signed with the commiter's gpg key. https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work Thoughts? -BEGIN PGP SIGNATURE- Version: APG v1.1.1 iQJRB

List subject prefix?

On many (most?) mailing lists, there is a prefix on all subjects which has the list name (such as [OpenWRT-Devel]) Can this prefix be added for this list (or is that an option that I missed when I signed up)? Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog,

A suggestion for the 'rules'; experimental/testing branch

Hi all, A personal aside; I seem to be doing better so hopefully I can be a positive factor in this project. Anyway, I read the rules and have one suggestion: There is no mechanism for removing problematic committers. Problematic can mean one person who makes the project miserable for the rest

Re: [OpenWrt-Devel] Introducing the LEDE project

On 4 May 2016 at 23:19, tapper wrote: > On 04/05/2016 21:01, mbm wrote: >> >> Dear OpenWrt community, >> >> It is with a great amount of surprise that, like all of you, we read >> about the announcement of the LEDE project yesterday, as there was no >> prior announcement nor clues this would happe

project goals

Hi all, Very happy to see this project reboot happening. An acknowledgement of the issues facing OpenWRT was long overdue. I'd like some clarity on some things that aren't explicitly mentioned in the stated goals, however. First off, is the SVN nonsense definitely gone now? Will the LEDE proj

download mirrors

Hi, few people asked me about rsync access. here is the url people should use to clone the downloads server. --> downloads.lede-project.org::downloads/ currently there is not much data present but i am sure that we will accumulate quite a bit over the coming months. as a start I will try to get

Re: Staging tree on Github

You can find the tree at https://github.com/lede-project/staging ~ Jo ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [PATCH] generic: Colorize the command line prompt

> This patch colorizes the command line prompt > > Signed-off-by: L. D. Pinney > --- > > package/base-files/files/etc/profile | 9 - > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/package/base-files/files/etc/profile b/package/base > -files/files/

Staging tree on Github

Hi all, there's some extremely popular demand to be able to contribute through Github and a while back we already decided to utilize staging trees in order to consolidate commits being made to master. Due to this I decided to open a staging tree on Github which you can do your PRs against. The p

Re: Usage of Github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thank you, Ted. I've started a mirror on gitlab. It should fetch commits every hour. https://gitlab.com/groups/lede -BEGIN PGP SIGNATURE- Version: APG v1.1.1 iQJRBAEBCgA7BQJXKjhCNBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs ZGV2ZWxvcGVyQGdtY

Re: [PATCH] style: use sans-serif font

Are you really thanking yourself for your patch here? ;) Cheers, Vittorio On 04/05/2016 13:12:37 CEST, Rafał Miłecki wrote: Applied, thanks Rafal. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede

Re: [PATCH] style: use sans-serif font

This wasn't Rafal but my Thunderbird virtual identity plugin copying random addresses :( It was me applying the patch here: http://git.lede-project.org/?p=web.git;a=commitdiff;h=7ebd2952f72c2b25439db828ce450673ace02faf ~ Jo ___ Lede-dev mailing list L

Re: OpenWRT tree vs LEDE tree

Greetings, Firstly all the best in your new endeavor. Secondly, I was planning to submit a set of patches to add support for TPLink Archer C2600 (QCA IPQ8064), originally authored by Bendavid, submitted to DD by Darryl - still pending, and finally updated for current trunk and patched for HW

Re: OpenWRT tree vs LEDE tree

Jo-Philipp Wich - 12:16 4.05.16 wrote: > Hi Michael, > > several people expressed the intention to continue pushing patches to > both trees. In any case we'll keep picking stuff from both lists for > LEDE for some time to come. Understood, thanks! ___

Re: OpenWRT tree vs LEDE tree

Hi Michael, several people expressed the intention to continue pushing patches to both trees. In any case we'll keep picking stuff from both lists for LEDE for some time to come. Regards, Jo-Philipp ___ Lede-dev mailing list Lede-dev@lists.infradead.or

Re: [PATCH] style: use sans-serif font

Applied, thanks Rafal. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

[PATCH] style: use sans-serif font

Using sans-serif is recommended for web pages as it makes text easier to read on screens. Signed-off-by: Rafał Miłecki --- css/lede.css | 4 1 file changed, 4 insertions(+) diff --git a/css/lede.css b/css/lede.css index 3c6f3d8..bb0abde 100644 --- a/css/lede.css +++ b/css/lede.css @@ -2,6

OpenWRT tree vs LEDE tree

Hi, I just wanted to ask, do you plan to merge changes and patches from OpenWRT as well from time to time or do you plan to go completely separate way? Just asking as I'm wondering whether to send patches (when I have some) just to OpenWRT (to prevent merge conflicts and make merging easier) or to