From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4357] New: prevent patch commands from accessing source control
Date: Sat, 22 Oct 2011 02:53:54 +0000 (UTC) [thread overview]
Message-ID: <bug-4357-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4357
Summary: prevent patch commands from accessing source control
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: d_mo1234 at yahoo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 3655
--> https://bugs.busybox.net/attachment.cgi?id=3655
patch file
A little while back, I ran into a problem compiling buildroot on an older
Ubuntu (9.xx I think), where patch was attempting to perform Perforce source
control operations. We had to fix this by adding -g0 to the patch script. I
think this may not be a problem on newer distributions, but perhaps it would be
good to ensure that patch doesn't attempt such ops in the future by using the
-g0.
The line that we fixed is in apply-patches.sh, but I noticed that there is also
a patch command in grub.mk too. I have attached a patch for both.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-10-22 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 2:53 bugzilla at busybox.net [this message]
2011-11-26 20:57 ` [Buildroot] [Bug 4357] prevent patch commands from accessing source control bugzilla at busybox.net
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=bug-4357-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.