All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] [ping] [patch] CONFIG_UPDATE for a few packages
Date: Tue, 12 Feb 2008 11:38:05 +1100	[thread overview]
Message-ID: <20080212003805.GA12409@cloud.net.au> (raw)
In-Reply-To: <200802102331.m1ANVuFi015689@sallyv1.ics.uci.edu>

On Sun, Feb 10, 2008 at 03:31:50PM -0800, Dan Nicolaescu wrote:
> I sent this patch over a month ago.  Nobody has made any comments, or
> applied it yet.
> The patch is pretty straight forward.... 

Your patch seems reasonable so I applied it.

> Is there a different way of submitting patches? Do I need to do
> something different?  Please let me know.

You can submit them to the bug/issue tracker on the web site.

>   > --- sed/sed.mk~
>   > +++ sed/sed.mk
>   > @@ -37,6 +37,7 @@
>   >  	mkdir -p $(HOST_SED_DIR)/bin
>   >  	$(SED_CAT) $(DL_DIR)/$(SED_SOURCE) | tar -C $(TOOL_BUILD_DIR) $(TAR_OPTIONS) -
>   >  	toolchain/patch-kernel.sh $(SED_DIR1) package/sed/ configure.patch
>   > +	$(CONFIG_UPDATE) $(SED_DIR1)/config
>   >  	touch $@
>   >  
>   >  $(SED_DIR1)/.configured: $(SED_DIR1)/.unpacked
>   > @@ -97,6 +98,7 @@
>   >  #############################################################
>   >  $(SED_DIR2)/.unpacked: $(DL_DIR)/$(SED_SOURCE)
>   >  	$(SED_CAT) $(DL_DIR)/$(SED_SOURCE) | tar -C $(BUILD_DIR) $(TAR_OPTIONS) -
>   > +	$(CONFIG_UPDATE) $(SED_DIR2)/config
>   >  	touch $(SED_DIR2)/.unpacked
>   >  
>   >  $(SED_DIR2)/.configured: $(SED_DIR2)/.unpacked
>   > --- autoconf/autoconf.mk
>   > +++ autoconf/autoconf.mk
>   > @@ -24,6 +24,7 @@
>   >  
>   >  $(AUTOCONF_SRC_DIR)/.unpacked: $(DL_DIR)/$(AUTOCONF_SOURCE)
>   >  	$(AUTOCONF_CAT) $(DL_DIR)/$(AUTOCONF_SOURCE) | tar -C $(TOOL_BUILD_DIR) $(TAR_OPTIONS) -
>   > +	$(CONFIG_UPDATE) $(AUTOCONF_SRC_DIR)
>   >  	touch $@

Unless you have an unusual host platform, it's not necessary to
$(CONFIG_UPDATE) for the autoconf host build.. but it's harmless so I
left it in.

Please send patches as attachments rather than in-line.

thanks,
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

      parent reply	other threads:[~2008-02-12  0:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04 17:53 [Buildroot] [patch] CONFIG_UPDATE for a few packages Dan Nicolaescu
2008-02-10 23:31 ` [Buildroot] [ping] " Dan Nicolaescu
2008-02-11 13:57   ` Thiago A. Corrêa
2008-02-12  0:38   ` Hamish Moffatt [this message]

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=20080212003805.GA12409@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.