From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6080] New: Git fetch caching
Date: Fri, 8 Mar 2013 04:22:25 +0000 (UTC) [thread overview]
Message-ID: <bug-6080-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6080
Summary: Git fetch caching
Product: buildroot
Version: 2012.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: acooks at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
When using the Custom Git tree kernel option, changes to the git repository are
not detected by buildroot. Even a 'make clean' doesn't remove the stale cached
sources.
Please provide a way to use a local git repo directly, without any caching.
--
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:[~2013-03-08 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 4:22 bugzilla at busybox.net [this message]
2013-03-08 8:35 ` [Buildroot] [Bug 6080] Git fetch caching bugzilla at busybox.net
2013-03-11 3:24 ` bugzilla at busybox.net
2013-05-26 13:34 ` bugzilla at busybox.net
2014-01-08 5:18 ` 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-6080-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.