If we import more and more files from various FreeBSD versions, then we
make it harder and harder to update everything to a newer FreeBSD
release. This may end up in a situation where we are practically stuck
at FreeBSD 9.
Imports which are not from the freebsd-org submodule must at least
clearly state the import version in the commit message.
On 14/07/16 07:38, yao0718 wrote:
I am not use the freebsd-orgsubmodule commit, I clone the master
freebsd form github and manual port form the master of freebsd
------------------ Original ------------------
*From: * "Sebastian Huber";<sebastian.hu...@embedded-brains.de>;
*Date: * Thu, Jul 14, 2016 01:35 PM
*To: * "Gedare Bloom"<ged...@rtems.org>; "yao0718"<29171...@qq.com>;
*Cc: * "devel"<devel@rtems.org>;
*Subject: * Re: [1/6]add ar8031 or ar 8035 phy support
On 13/07/16 16:41, Gedare Bloom wrote:
> I think this should be the checked-out version of specific freebsd,
> with the populated $FreeBSD$ tag? See what other files are using.
In the libbsd the FreeBSD version is determined by the Git freebsd-org
submodule commit.
Is the Git freebsd-org submodule the origin of this file?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
