Re: [Libreoffice] [PUSHED] fix xml2cmp build with svn gcc

Miklos Vajna <vmiklos -AT- frugalware.org>
Thu, 11 Aug 2011 17:17:32 +0200

On Thu, Aug 11, 2011 at 09:09:39AM -0600, Tom Tromey <tromey@redhat.com> wrote:

Noel> I rolled up this patch and the previous one here
Noel> 
http://cgit.freedesktop.org/libreoffice/core/commit/?id=c2a634416ba8f385c25c16cc52aeae6f68cab9db

I don't understand where these commits go.
I re-pulled in 'ure' (actually everywhere using ./g pull) but I don't
see that commit.  I'm on 'master', should I be using some other branch?


Yes, core.git. See

http://wiki.documentfoundation.org/Development/Native_Build#Getting_the_sources

Background: http://wiki.documentfoundation.org/Development/One_Git_Conversion

Attachment: pgp5HFL3kT_Dz.pgp
Description: PGP signature

Context

[Libreoffice] [PATCH] fix xml2cmp build with svn gcc · Tom Tromey
- Re: [Libreoffice] [PATCH] fix xml2cmp build with svn gcc · Norbert Thiebaud
  - Re: [Libreoffice] [PUSHED] fix xml2cmp build with svn gcc · Noel Power
    - Re: [Libreoffice] [PUSHED] fix xml2cmp build with svn gcc · Tom Tromey
      - Re: [Libreoffice] [PUSHED] fix xml2cmp build with svn gcc · Miklos Vajna
        
        Re: [Libreoffice] [PUSHED] fix xml2cmp build with svn gcc · Tom Tromey
        
        Re: [Libreoffice] [PUSHED] fix xml2cmp build with svn gcc · Michael Meeks
      - Re: [Libreoffice] [PUSHED] fix xml2cmp build with svn gcc · Kohei Yoshida
      - Re: [Libreoffice] [PUSHED] fix xml2cmp build with svn gcc · Noel Power
  - Re: [Libreoffice] [PATCH] fix xml2cmp build with svn gcc · Tom Tromey

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.