Hi,
On Tue, Feb 18, 2014 at 04:57:39PM +0100, Bjoern Michaelsen wrote:
P.S.: We current have two gnu make forks in dev-tools, one in the gnu-make-lo
      repository on gerrit, were one cant push to. Such a mess. When nobody
      protests, I will delete the copies in dev-tools and make the gnu-make-lo
      repository writable. Whatever forking had been done there and is still of
      value needs to be pushed on proper branches there then.
Discussed this with Norbert on IRC and moved the dev-tools copies to gnu-make-lo proper. So
  (repo/branch/dir)
  dev-tools/master/make-3.81        moved to gnu-make-lo/gnu-make-lo-3.81/.
    https://gerrit.libreoffice.org/gitweb?p=gnu-make-lo.git;a=shortlog;h=refs/heads/gnu-make-lo-3.81
  dev-tools/master/make-3.82-gbuild moved to gnu-make-lo/gnu-make-lo-3.82/.
    https://gerrit.libreoffice.org/gitweb?p=gnu-make-lo.git;a=shortlog;h=refs/heads/gnu-make-lo-3.82
  dev-tools/master/make-4.0-gbuild moved to gnu-make-lo/gnu-make-lo-4.0/.
    https://gerrit.libreoffice.org/gitweb?p=gnu-make-lo.git;a=shortlog;h=refs/heads/gnu-make-lo-3.82
and the new depcache branch is now at gnu-make-lo repo, branch feature/depcache:
  https://gerrit.libreoffice.org/gitweb?p=gnu-make-lo.git;a=shortlog;h=refs/heads/feature/depcache
I will delete the dirs in dev-tools soonish, and put a README.gnumake there pointing to the new 
location.
@Norbert: Can you easily make gnu-make-lo replicate too (primarily to Github/Gitorious?).
Best,
Bjoern
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.