From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Denk Date: Mon, 23 Nov 2009 21:03:01 +0100 Subject: [U-Boot] [PATCH 0/5] Introducing TI's New SoC/board AM3517EVM In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D942DC993@dlee01.ent.ti.com> References: <1258974495-28027-1-git-send-email-hvaibhav@ti.com> <0554BEF07D437848AF01B9C9B5F0BC5D942DC993@dlee01.ent.ti.com> Message-ID: <20091123200301.33D253F6D6@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear "Paulraj, Sandeep", In message <0554BEF07D437848AF01B9C9B5F0BC5D942DC993@dlee01.ent.ti.com> you wrote: > > I hope you made the patches against the current u-boot-ti/master Please note that this is a tendency I seriously dislike. Please do NOT do this. Please see bullet # 3 at http://www.denx.de/wiki/U-Boot/Patches : Please use the "master" branch of the mainline U-Boot git repository (git://git.denx.de/u-boot.git) as reference, unless (usually late in a release cycle) there has been an announcement to use the "next" branch of this repository instead. If we see patches againt any of 30 or so custodian trees, which don't apply against the "official" master tree, we will see chaos pretty soon. Please let's make sure there is only minimal difference between custdian trees and "master" (or "next"), so there is no reason to use custodian tress as reference for patches instead. Please _always_ use "master" (or "next") as base for patches! Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de A Perl script is correct if it's halfway readable and gets the job done before your boss fires you. - L. Wall & R. L. Schwartz, _Programming Perl_