[gobolinux-users] Rationales for patches in recipes? (was: Re: gobohide not working - linux-2.6.21.1)

[Carlo Calica]

On 6/28/07, hisham.hm at gmail.com <hisham.hm at gmail.com> wrote:
> On 6/28/07, MJ Ray <mjr at phonecoop.coop> wrote:
> > Isaac Dupree <isaacdupree at charter.net> wrote:
> > > It would be nice if there were a standard way to document the rationale
> > > for adding each patch (beyond the filename of the patch) [...]
> >
> > man patch says "patch tries to skip any leading garbage," so we could
> > just write it above the patch header...  I'll try it next time I patch.
>
> Yes, I've done this a few times (you may find it in some recipes),
> it's a great way to document a patch.
>

Is it obvious though?  Also, it wouldn't match my recipe workflow.  I
typically diff foo.orig foo >.../01-bar.patch when upgrading versions.
 I would now need to use a temp file and some additional editing.  An
external 01-bar.readme could list rationale, upstream source, whatever
without risk of loosing that data.  Probably easier for RecipeLint to
check too.

-- 
Carlo J. Calica