All,
Just a note, we've created a branch on top of the freetype 2.3.8
release at http://svn.ghostscript.com/ghostscript/trunk/freetype so we
can work on our own fixes before trying to push them upstream. Right
now (r9528) it:
* enables the incremental font support
* enables tracing, since we're d
On Tue, Mar 3, 2009 at 6:03 AM, Werner LEMBERG wrote:
> . git format-patch
> . editing commit messages in the *.patch files
> . git am --rebasing --whitespace=nowarn *.patch
>
> works fine, however, it loses all tags created by parsecvs.
Presumedly this is because changing the log message
David Turner wrote:
Hello,
I'm currently updating the Android FreeType sources to the latest CVS.
In doing so, I noticed something that unfortunately
escaped me before that: we added a new field to a publicly declared
structure, thus breaking the ABI.
More specifically, the declaration of PS
> Werner, if you are overworked, I'd like to prepare the release
> myself.
I can afford time, fortunately, so please check whether everything is
in shape, and I'll do a release in a few days.
It seems that you have some spare time right now -- may I ask that you
walk over the open Savannah bug r
>> > Would it make sense to first convert to GIT then later change the
>> > commit messages there.
>>
>> I tried that, and it doesn't work properly.
>
>
> Ah, can you tell me which problem exactly? I could do the migration
> myself.
First of all, parsecvs is a nice tool, but it is a bit awkward
This is done, I'm preparing a message to send to freetype-announce.
Werner, if you are overworked, I'd like to prepare the release myself. Are
there specific steps I need to know to do that ?
Thanks
2009/3/3 David Turner
> It'd be nice if we could remove the 2.3.8 packages from the Savannah
>
It'd be nice if we could remove the 2.3.8 packages from the Savannah server.
I'll try to do that.
2009/3/3 Werner LEMBERG
>
> > I have submitted a fix to the CVS repository (which wasn't too
> > trivial).
>
> Thanks. I'll release a new FreeType version probably in a week or so.
>
>
>Werner
2009/3/3 Werner LEMBERG
>
> > Would it make sense to first convert to GIT then later change the commit
> > messages there.
>
> I tried that, and it doesn't work properly.
>
Ah, can you tell me which problem exactly ? I could do the migration myself.
By the way, I started documenting it at the fo
> I have submitted a fix to the CVS repository (which wasn't too
> trivial).
Thanks. I'll release a new FreeType version probably in a week or so.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/
> David B., any chance to provide a fix?
Ah, David T. was quicker :-)
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
2009/2/25 Jean-Claude Repetto
> David Turner a écrit :
>
>> This has been recently fixed in the CVS repository, see this for details:
>>
>> http://git.freetype.org/?p=freetype2.git;a=commitdiff;h=7bb1c4ce1221edb3ed900666fee3eae790255820
>>
>>
> Hello,
>
> Thanks to mpsuzuki, Werner and David for
> Would it make sense to first convert to GIT then later change the commit
> messages there.
I tried that, and it doesn't work properly.
> I believe it's going to be much easier, and to be honest, I'm unsure
> that updating the original CVS messages is going to be very useful.
In case I don't f
Hi David,
that's ok, but I'm surprised this didn't get caught. The problem is even
worse than I thought because PS_FontInfoRec is
also used to define the "fonts_infos" in the PS_BlendRec structure (I don't
think we have any client code that accesses
this though).
I have submitted a fix to the CVS
> I would have used an alternative approach if I had been informed
> that adding a new field to the public structure was not permitted.
I also thought that it works without problems. Sigh. I *hate* ABI.
David B., any chance to provide a fix?
Werner
_
Hi Werner,
2009/3/3 Werner LEMBERG
>
> the `empty log message' problem in the conversion from CVS to git
> still bites me. It is far more trickier than expected :-(
>
> The steps I've suggested in a previous mail (using parsecvs, then `git
> format-patch' & `git am') works in principle. Howeve
David,
My apologies, but this was discussed on the development mailing list
(see below).
I would have used an alternative approach if I had been informed that
adding a new field to the public structure was not permitted.
David %^>
-Original Message-
From: Werner LEMBERG [
Hello,
I'm currently updating the Android FreeType sources to the latest CVS. In
doing so, I noticed something that unfortunately
escaped me before that: we added a new field to a publicly declared
structure, thus breaking the ABI.
More specifically, the declaration of PS_FontInfoRec in
include/f
Folks,
the `empty log message' problem in the conversion from CVS to git
still bites me. It is far more trickier than expected :-(
The steps I've suggested in a previous mail (using parsecvs, then `git
format-patch' & `git am') works in principle. However, tags created
by parsecvs are lost.
18 matches
Mail list logo
