Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi Rob,

On Sun, Feb 17, 2013 at 12:50:40AM +0100, Rob Snelders <programming@ertai.nl> wrote:
There is a Website repository on FDO. But as far as I know it is only
used for the bugassistant. The cgit reports that this repo is obsolete
but it isn't. Also is there a lot of stuff that isn't used anymore.

If you are sure that a branch is not used, I think you're allowed to
delete it with 'git push origin :branch_name'.

Can this repo be cleaned up? And the obsolete-tag be removed. Or can
we move the bugassistant to a other repo so it isn't tagged as obsolete.

Right now modifying the description of a repo isn't easy, hopefully
Michael can help with that. :)

Also after last change I get this error when pushing patches:
"remote: grep: hooks/obsolete-tags: No such file or directory"
I can push to the repo however so it isn't a big problem.

This is easier, the git hooks are now in git, I just submitted:

https://gerrit.libreoffice.org/2220

to fix that.

Thanks for reporting!

Miklos

-- 
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

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.