git checkout . in the other
> checkouts after I made some changes).
Even better :)
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf
Of Felix Fietkau
Sent: Friday, April 18, 2014 8:02 AM
To: Karl P; openwrt-devel@lists.openwrt.org
Subjec
On 04/18/2014 03:01 PM, Felix Fietkau wrote:
On 2014-04-18 15:59, Karl P wrote:
I have never used the version part of this file actually, I use it solely to set
the source path to a local tree. I use this for packages that I develop both
snip
Right, that is a valid usecase, but package-ver
On 2014-04-18 15:59, Karl P wrote:
>
>
> On 04/18/2014 12:04 PM, Felix Fietkau wrote:
>> On 2014-04-17 21:12, Mathieu Olivari wrote:
>>> This feature is actually quite useful. Obviously it's an opt-in approach
>>> from a package standpoint, but it's pretty useful to swap package
>>> versions as w
On 04/18/2014 12:04 PM, Felix Fietkau wrote:
On 2014-04-17 21:12, Mathieu Olivari wrote:
This feature is actually quite useful. Obviously it's an opt-in approach
from a package standpoint, but it's pretty useful to swap package
versions as well as pulling components TOT. In that case, working
On 2014-04-17 21:12, Mathieu Olivari wrote:
> This feature is actually quite useful. Obviously it's an opt-in approach
> from a package standpoint, but it's pretty useful to swap package
> versions as well as pulling components TOT. In that case, working
> directly on the GIT tree by enabling that
: openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] [PATCH 1/4] include: Restore
package-version-override.mk
Seconded, I was hoping to send a patch restoring this as well.
One point though, you should include the fix in:
https://lists.openwrt.org/pipermail/openwrt-devel/2014-April
Seconded, I was hoping to send a patch restoring this as well.
One point though, you should include the fix in:
https://lists.openwrt.org/pipermail/openwrt-devel/2014-April/024605.html
I'm open to alternative suggestions of workflow to not need this, but when I'm
working on application code,
This feature is actually quite useful. Obviously it's an opt-in approach
from a package standpoint, but it's pretty useful to swap package
versions as well as pulling components TOT. In that case, working
directly on the GIT tree by enabling that option is sometimes seen as a
more flexible way than