All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nataraj S Narayan <nataraj@vaaraahi.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR: patching  diff f7abec2d1d1e5... direct
Date: Fri, 18 Mar 2011 11:04:59 +0000	[thread overview]
Message-ID: <4D833C5B.4090604@vaaraahi.com> (raw)

Hi

I was trying to patch the diff of commit
f7abec2d1d1e52f49f7d95c48165cde8cf41edb6 (patch) by 	Jean-Christophe
PLAGNIOL-VILLARD, in the 'package' dir of buildroot.

I believe I am making some mistake here.

# patch -p1< Makefile.package.in.patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/package/Makefile.package.in
|+++ b/package/Makefile.package.in
--------------------------
File to patch:
Skip this patch? [y] n
File to patch: Makefile.package.in
patching file Makefile.package.in
patch: **** malformed patch@line 4: define DOWNLOAD_GIT


Plz help me to do this right.


regards

Nataraj

             reply	other threads:[~2011-03-18 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 11:04 Nataraj S Narayan [this message]
2011-03-19  7:24 ` [Buildroot] BR: patching diff f7abec2d1d1e5... direct Thomas Petazzoni

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=4D833C5B.4090604@vaaraahi.com \
    --to=nataraj@vaaraahi.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.