Hey
As discussed again in today's call, I've pushed a git mirror of edk2's and edk2-fatdriver2's SVN modules to git.linaro.org.
This is temporary in that: * the whole history of edk2-fatdriver2 was imported, but only the last revision of edk2 was imported (a full import is running, but that will take a while) * git.linaro.org lacks git-svn and has outbound traffic firewalled; I'm working with IS to resolve this
These can be used right now, with the caveats that the branches might be rebased or might move to another host; I'm happy to assist if you need help moving your patches around when that happens.
The repos are: git://git.linaro.org/mirror/edk2/edk2.git git://git.linaro.org/mirror/edk2/edk2-fatdriver2.git
These were created with: git svn clone -s \ https://edk2-fatdriver2.svn.sourceforge.net/svnroot/edk2-fatdriver2 edk2-fatdriver2 git svn clone -r 12354 -s \ https://edk2-fatdriver2.svn.sourceforge.net/svnroot/edk2 edk2
Would you need any other SVN module mirrored, or if you have suggestions about a different set of git-svn options, please get in touch with me.
Cheers
On Thu, Sep 15, 2011, Loïc Minier wrote:
The repos are: git://git.linaro.org/mirror/edk2/edk2.git git://git.linaro.org/mirror/edk2/edk2-fatdriver2.git
The contents of the repositories changed; the old ones are under mirror/old. The new ones expose the imported directly in the main namespace (e.g. main branch is "trunk" not "remotes/trunk" and there isn't an additional "master").
These are updated hourly.
On Fri, 2011-09-23 at 15:30 +0200, Loïc Minier wrote:
On Thu, Sep 15, 2011, Loïc Minier wrote:
The repos are: git://git.linaro.org/mirror/edk2/edk2.git git://git.linaro.org/mirror/edk2/edk2-fatdriver2.git
The contents of the repositories changed; the old ones are under mirror/old. The new ones expose the imported directly in the main namespace (e.g. main branch is "trunk" not "remotes/trunk" and there isn't an additional "master").
These are updated hourly.
How are these repositories expected to be used? Is the idea that they get cloned by teams/people working on edk2 and this will save them the hassle of dealing with svn? (Unless they're involved in upstreaming work of course.)
Hi
On Fri, Sep 23, 2011, Jon Medhurst (Tixy) wrote:
How are these repositories expected to be used? Is the idea that they get cloned by teams/people working on edk2 and this will save them the hassle of dealing with svn? (Unless they're involved in upstreaming work of course.)
These can be useful in multiple ways. For people working on the upstream edk2 bits, they can start from the git repo instead of SVN; it's longer to checkout the git repo (5 minutes here), but you get the benefits of git (distributed SVN, cheap branches etc.). They can start from the mirror and configure the original SVN repo as a remote and directly commit their git patches as commits upstream.
The other way this can be useful is for ARM or Linaro to offer their branches of edk2. Currently, one has to apply patch files manually before building edk2 for ARM. These could be pre-committed in an edk2-arm.git repo which would be regularly rebased on edk2.git. The same goes for a Linaro branch where we could add support for this or that extra platform or toolchain or develop new features.
Did you have other uses in mind?
On Fri, 2011-09-23 at 17:06 +0200, Loïc Minier wrote:
Hi
On Fri, Sep 23, 2011, Jon Medhurst (Tixy) wrote:
How are these repositories expected to be used? Is the idea that they get cloned by teams/people working on edk2 and this will save them the hassle of dealing with svn? (Unless they're involved in upstreaming work of course.)
These can be useful in multiple ways. For people working on the upstream edk2 bits, they can start from the git repo instead of SVN; it's longer to checkout the git repo (5 minutes here), but you get the benefits of git (distributed SVN, cheap branches etc.). They can start from the mirror and configure the original SVN repo as a remote and directly commit their git patches as commits upstream.
The other way this can be useful is for ARM or Linaro to offer their branches of edk2. Currently, one has to apply patch files manually before building edk2 for ARM. These could be pre-committed in an edk2-arm.git repo which would be regularly rebased on edk2.git. The same goes for a Linaro branch where we could add support for this or that extra platform or toolchain or develop new features.
Did you have other uses in mind?
It was the second use I had in mind, and the first also sounds handy. Thanks for explaining.
boot-architecture@lists.linaro.org
-
Jon Medhurst (Tixy) -
Loïc Minier