All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] What is the proper procedure to commit a patch?
Date: Sat, 7 Jul 2007 14:35:36 +0200	[thread overview]
Message-ID: <20070707123536.GS4096@aon.at> (raw)
In-Reply-To: <00c201c7c091$e527cc10$dcc4af0a@atmel.com>

On Sat, Jul 07, 2007 at 01:16:13PM +0200, Ulf Samuelsson wrote:
>>>Now we have package/linux.mk and we have Linux configuration spread out.
>>>
>>>What I want to do is to move "package/linux.mk" to "package/linux/linux.mk"
>> 
>> What's that good for? Just curious, this is just cosmetics.
>> 
>>>and then remove the distributed linux configuration to "package/linux/Config.in"
>> 
>> Which "distributed linux configuration" do you mean?
>>
>
>I'd like to have the configuration and makefile in the same directory.

I don't like to have it in the same directory.

>Now the configuration is in a different directory.

Yes, and that's a feature. You (or the board) can easily set
BR2_PACKAGE_LINUX_KCONFIG to anything you want. It was added for exactly
this purpose.

>
>The current linux.mk is much less flexible than the one I use.

You keep saying this, ISTR.
What does not work currently as opposed to "yours"?

Did you try to use the currently existing one, recently?

>Once we have the linux in a good place, then I will submit
>my proposals to the mailing list.

  reply	other threads:[~2007-07-07 12:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 12:35 [Buildroot] What is the proper procedure to commit a patch? Ulf Samuelsson
2007-07-06 15:26 ` Bernhard Fischer
2007-07-06 15:36   ` Ulf Samuelsson
2007-07-07 10:12     ` Bernhard Fischer
2007-07-07 11:16       ` Ulf Samuelsson
2007-07-07 12:35         ` Bernhard Fischer [this message]
2007-07-07 13:46           ` Ulf Samuelsson
2007-07-06 15:55 ` Steven J. Hill
2007-07-06 21:10   ` Ulf Samuelsson
2007-07-07 10:06   ` [Buildroot] $(TARGET_CONFIGURE_OPTS) $(MAKE) vs $(MAKE) $(TARGET_CONFIGURE_OPTS) Ulf Samuelsson
2007-07-07 13:01     ` Bernhard Fischer
2007-07-07 16:06       ` Ulf Samuelsson
2007-07-07 17:29         ` Bernhard Fischer
2007-07-07 19:37           ` Ulf Samuelsson
2007-07-07 21:16             ` Bernhard Fischer
2007-07-07 22:49               ` Ulf Samuelsson
2007-07-09  8:25                 ` Bernhard Fischer
2007-07-09  9:21                   ` Bernhard Fischer
2007-07-09 12:20                     ` Steven J. Hill
2007-07-09 13:41                       ` Julien Letessier
2007-07-09 13:08                         ` Ulf Samuelsson
2007-07-09 16:33                         ` Bernhard Fischer
2007-07-10 11:51                           ` Julien Letessier
2007-07-10 18:24                             ` Bernhard Fischer
2007-07-07 10:21 ` [Buildroot] What is the proper procedure to commit a patch? Bernhard Fischer

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=20070707123536.GS4096@aon.at \
    --to=rep.dot.nop@gmail.com \
    --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.