Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: do_patch fails if path starts with ./
Date: Thu, 12 Mar 2009 14:40:37 -0400	[thread overview]
Message-ID: <20090312184037.GA1109@denix.org> (raw)
In-Reply-To: <ac9c93b10903120130v5c19e5fbq224df848792f3a5f@mail.gmail.com>

On Thu, Mar 12, 2009 at 09:30:47AM +0100, Frans Meulenbroeks wrote:
> Hi,
> 
> When generating my (normally small) patches I typically do a cp file
> file.orig in the work dir, then change file and at the end do a diff
> -urN path/file.oirg path/file >file.patch
> no probllems with that (although if there are recommendations to do
> things simpler/better, I'm of course open to suggestions).
> 
> However yesterday I copied and pasted filenames and ended up with
> diff -urN ./path/file.orig ./path/file >file.patch

Have you tried:
diff -urN path/file.orig path/file >file.patch

> of course then in file.patch the filenames starts with ./
> when that happens do_patch does not find the file.(probably because it
> thinks there is an additional directory because it does not see that
> ./ is actually the same dir)

You may want to play with the pnum variable (increase it?) in the SRC_URI 
of the patch...

> is this a bug in our build system? or in patch?
> or should I just avoid using ./ if I create a patch?
> 
> btw: I alredy tried diff -Nurd (so an additional d flag) but that did
> not make a difference).

-- 
Denys



      parent reply	other threads:[~2009-03-12 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12  8:30 do_patch fails if path starts with ./ Frans Meulenbroeks
2009-03-12 10:09 ` Marcin Juszkiewicz
2009-03-12 18:40 ` Denys Dmytriyenko [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=20090312184037.GA1109@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox