Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Changed download links for libxml2 and libxslt
Date: Sun, 10 Mar 2019 19:10:47 +0100	[thread overview]
Message-ID: <20190310191047.0cf0e32b@gmx.net> (raw)
In-Reply-To: <CAJSYY8c0iKO9s=xExwu9bLvdJb1g2r3-vBuU3_6KGUr2SKN0sQ@mail.gmail.com>

Hello Nityananda,

On Sun, 10 Mar 2019 14:51:18 +0530, Nityananda Padhan <ntneitin@gmail.com> wrote:

> Do I have to send the Patch again with buildroot at buildroot.org as CC?

Not sure, but I think yes (and try to send the patches via git send-email as
described in [1]) to make sure the patches hit the buildroot patchwork ([2])
which is used by the buildroot maintainers/committers...

Your can add the Reviewed-by to the patches before sending...

Regards,
Peter

[1] https://buildroot.org/downloads/manual/manual.html#submitting-patches
[2] https://patchwork.ozlabs.org/project/buildroot/list/


> 
> On 10/03/2019, Peter Seiderer <ps.report@gmx.net> wrote:
> > Hello Nityananda,
> >
> > thanks for the rework, patch looks good, but please keep
> > buildroot at buildroot.org in CC...
> >
> > Reviewed-by: Peter Seiderer <ps.report@gmx.net>
> >
> > Regards,
> > Peter
> >
> > On Sat, 9 Mar 2019 18:59:16 +0530, Nityananda Padhan <ntneitin@gmail.com>
> > wrote:
> >  
> >> From dc92f5d7088a9c1c5be0151f2736df900db35e70 Mon Sep 17 00:00:00 2001
> >> From: Nityananda Padhan <ntneitin@gmail.com>
> >> Date: Sat, 9 Mar 2019 18:50:05 +0530
> >> Subject: [PATCH 2/2] package/libxslt: change download site to http
> >>
> >> Changes to be committed:
> >> modified:   package/libxslt/libxslt.mk
> >>
> >> Signed-off-by: Nityananda Padhan <ntneitin@gmail.com>
> >> ---
> >>  package/libxslt/libxslt.mk | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/package/libxslt/libxslt.mk b/package/libxslt/libxslt.mk
> >> index 5b1c0ae268..4632301b16 100644
> >> --- a/package/libxslt/libxslt.mk
> >> +++ b/package/libxslt/libxslt.mk
> >> @@ -5,7 +5,7 @@
> >>
> >> ################################################################################
> >>
> >>  LIBXSLT_VERSION = 1.1.32
> >> -LIBXSLT_SITE = ftp://xmlsoft.org/libxslt
> >> +LIBXSLT_SITE = http://xmlsoft.org/sources
> >>  LIBXSLT_INSTALL_STAGING = YES
> >>  LIBXSLT_LICENSE = MIT
> >>  LIBXSLT_LICENSE_FILES = COPYING  
> >
> >  

  parent reply	other threads:[~2019-03-10 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 10:16 [Buildroot] [PATCH 1/1] Changed download links for libxml2 and libxslt Nityananda Padhan
2019-03-08 22:41 ` Peter Seiderer
     [not found]   ` <CAJSYY8fUi_chaMOAYPe3whv8c7enG0UxuDFxnaFaR4WFeU31xw@mail.gmail.com>
2019-03-09 20:53     ` Peter Seiderer
2019-04-02 20:33       ` Peter Korsgaard
     [not found]     ` <CAJSYY8cDvs-X_pJBvU7o1hDojbXsTerbNqyV3aCLtEg9-xNtJQ@mail.gmail.com>
2019-03-09 20:55       ` Peter Seiderer
     [not found]         ` <CAJSYY8c0iKO9s=xExwu9bLvdJb1g2r3-vBuU3_6KGUr2SKN0sQ@mail.gmail.com>
2019-03-10 18:10           ` Peter Seiderer [this message]
2019-04-02 20:33         ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190310191047.0cf0e32b@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox