Gna does, but you can only have one repo per project and it takes them forever to respond if you need to modify it. I don't recommend gna unless you're comfortable with that.
Actually if you create a repo on github, https://git.gnu.io or equivalent that would be perfect for the Weston part of the changes. For back I would recommend creating a branch in our existing repo which would allow us to figure out how we can get it into the main line. A full fork is too much. GC On Thu, Jan 14, 2016 at 10:27 Sergio L. Pascual <s...@sinrega.org> wrote: > On Wed, 2016-01-13 at 20:18 -0500, Gregory Casamento wrote: > > I am indescribably excited about this. It looks awesome. Just a > > few little quirks! Wayland is definitely the way forward. Please > > consider putting this up on in the repo on gna.org as this is an > > awesome development. > > This project requires changes in both core/back and weston. For weston, > the easiest way for me would be forking it and keeping a separate git repo > elsewhere (does gna.org offer git repos?). > > What is the preferred way to publish the changes in core/back? Sending > patches to the mailing list? A separate branch? A full fork to be > merged in a future? > > Sergio. > >
_______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
