On Fri, Apr 18, 2014 at 9:32 PM, Jerome Leclanche <adys...@gmail.com> wrote: > Hi list > > Git mirroring is fully set up and every repository has been updated. > **Please update your remotes immediately and do NOT push to Github > anymore**. I'm looking into whether it's possible to make the Github > repositories write only to avoid mistakes. Unfortunately, it looks > like anyone in the Owners team will always be able to write to all > repos. > If you do push to Github by mistake, please immediately push to > git.lxde.org as well and barring conflicts, things should work just > fine. Cool!!! Finally it's done. The next is our bug tracker. :-)
> Pushes to Github are handled by our little mascot Helix: > https://github.com/HelixBot - I'm the only one with access to the > account currently, but if anyone wants the password just ask me (I'm > also looking into whether it's possible to set up delegated > management). On that note, Helix is currently set up with an > @leclan.ch email and I would like to update it to get an @lxde.org > email. > > Whenever you push to a repository on git.lxde.org, the server will > immediately mirror push everything on github.com/LXDE. > I've left instructions in ~git/README on how to set up new > repositories with this mirroring scheme. > > The AUR has also been updated to directly use the git.lxde.org repositories. > > NOTES: > Repos not set up: > https://github.com/lxde/jhbuild This one need some more work. The config files need to be changed to use the new git repos. > https://github.com/lxde/lxrandr-qt This one is deprecated. We should use lxqt-config-randr. I removed that repo from github.com/lxde and move it to my own page for backup purpose. > I can't find those in the lxde.org project list. @PCMan, what do we do > about them? > libfm.git had a lot of branches on github which have been deleted > after the sync. They all seem to be old, unused branches (filter, > fm-path-gsequence, search-monitor, thumbnails, ...) but it's worth > mentioning. Please confirm with Andriy G (LStranger) before you delete any branch. AFAIK, he is using some of them but I'm not sure which ones are still needed. I personally don't use the old branches anymore. > Also, all of this poses a problem regarding pull request; we should no > longer use the Merge button on github. Personally I'm fine with that > as I do not like the "Merge" commits it produces, I would rather we > keep the history clean and pull the PRs locally, rebase them if > necessary and push them upstream. > If others are fine with this I'd love to figure out a way to do this > cleanly and easily maybe through a git alias or two. > > J. Leclanche > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/NeoTech > _______________________________________________ > Lxde-list mailing list > Lxde-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxde-list ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
