All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: Integrate latest yaffs2
Date: Wed, 25 Apr 2012 15:40:51 -0700	[thread overview]
Message-ID: <4F987D73.5060805@ti.com> (raw)
In-Reply-To: <201204261028.44543.manningc2@actrix.gen.nz>

On 04/25/2012 03:28 PM, Charles Manning wrote:
> On Thursday 26 April 2012 10:21:37 Tom Rini wrote:
>> On Thu, Apr 26, 2012 at 09:08:42AM +1200, Charles Manning wrote:
>>> On Tuesday 24 April 2012 08:58:09 you wrote:
>>>> Dear Charles Manning,
>>>>
>>>> In message<201204231346.32195.manningc2@actrix.gen.nz>  you wrote:
>>>>> I recently sent a message to the list announcing a method for
>>>>> patching in the latest yaffs2.
>>>>>
>>>>> u-boot updated with the latest yaffs2 can be pulled from
>>>>> git at github.com:cdhmanning/u-boot-yaffs2.git
>>>>
>>>> Please read http://www.denx.de/wiki/U-Boot/Patches and post proper
>>>> patch(es) for review.
>>>
>>> At least one of the files exceeds the 100k patch limit.
>>>
>>> I know you'd like patches, but there are two really easy options for
>>> someone on the inside to do this:
>>>
>>> 1) Run the script off the yaffs git
>>> -or-
>>> 2) Merge from the https://github.com/cdhmanning/u-boot-yaffs2
>>
>> So this means things have gotten really far out of sync.  Would you be
>> willing to say that in the future you'll be submitting regular well
>> formatted and broken down patches like I assume you do in the yaffs2
>> tree itself so we can avoid this in the future?
>
> yaffs went through a large reformat a while ago meaning that the current code
> does not diff well against the old code. Future changes shuld be a lot easier
> to handle with direct patching.
>
> yaffs changes typically don't go through the yaffs  list since people with
> direct git checkin access do 95-99% of the changes.

Right, but a proper set of individual patches could be posted and 
reviewed in the future, yes?

-- 
Tom

  reply	other threads:[~2012-04-25 22:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  1:46 [U-Boot] Pull request: Integrate latest yaffs2 Charles Manning
2012-04-23 20:58 ` Wolfgang Denk
2012-04-25 21:08   ` Charles Manning
2012-04-25 22:21     ` Tom Rini
2012-04-25 22:28       ` Charles Manning
2012-04-25 22:40         ` Tom Rini [this message]
2012-04-25 22:47           ` Charles Manning
2012-04-26 12:25         ` Wolfgang Denk
2012-04-26 22:59           ` Charles Manning
2012-04-26 23:05             ` Graeme Russ
2012-04-27  6:35               ` Wolfgang Denk
2012-04-27  6:33             ` Wolfgang Denk

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=4F987D73.5060805@ti.com \
    --to=trini@ti.com \
    --cc=u-boot@lists.denx.de \
    /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.