On Sun, Mar 4, 2012 at 9:25 AM, Frederic Bouvier <fredfgf...@free.fr> wrote:
> > As a migration path, I verified that my changes to simgear are
> > compatible with the current next branch. If there is no objection,
> > I will commit these changes to gitorious and begin to prepare
> > the flightgear code in a way that would allow to keep the current
> > renderer.
>
> As I received no objections, I will commit my addition to simgear later in
> the day. You'll be warn ;-)
Speaking not-as-a-git-guru, would it make sense to push the rembrandt
changes into a separate "rebrandt" branch initially and keep that merged
with the "next" branch? It would make it easier for developers to check
out that branch and build it and if things look pretty reasonable we could
merge things into "next"? Just trying to be helpful here, and not make
things any more complicated.
Curt.
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
