[ft-devel] Git master has fix for CMake build header installation on Windows

[Nikolaus Waxweiler]

Hi list,
I broke the CMake build header installation on Windows in my clean-up. 
Fixed in master.


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel

[ft-devel] git advice Re: Freetype-devel Digest, Vol 151, Issue 17

[Hin-Tak Leung]

> Date: Wed, 09 Aug 2017 12:01:11 +0200
> (CEST)
> From: Werner LEMBERG 
> To: kkusha...@gmail.com
> Cc: freetype-devel@nongnu.org
> Subject: [ft-devel] more on the
> preferred setup for `make tests'
 
> [*] BTW, please don't use tabs within
> the FreeType project except in
>     Makefiles! 
> Similarly, please avoid trailing spaces, and the last
>     line in a text file
> should always be ended with a newline
>     character.


It is perhaps unfair to ask without show how :-). If you do

git config --global color.ui true

Many of git's command output (show, diff, etc) would be colorized. This makes 
life easier as it would colorize trailing spaces as red for example, and 
perhaps also mixed-use of space and tabs.

See also the core.whitespace entry in 'man git-config' and also the 
color.diff.whitespace section. 

___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel

[ft-devel] git repository for FreeType documentation

[Werner LEMBERG]

Folks,


the git repository of all FreeType documentation files is now
available online:

  http://cgit.freedesktop.org/freetype/freetype-web


Werner

___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: [ft-devel] git

[David Turner]

Welcome back tom :-)
In my opinion, reading the following is a definitive requirement for anyone
working with git:
http://eagain.net/articles/git-for-computer-scientists/

Git is very flexible, but the mental model one requires to maintain to use
it is much more demanding than traditional VCSes.

I also recomment the Git Community Book for new-comers:
http://book.git-scm.com/

Git has evolved historically from a low-level plumbing tool for real cowboy
developers to what it currently is; which is something with a very clunky
user interface where making a mistake is extremely easy, and reverting or
understanding what happened can be non trivial. Also, a lot of the git
tutorials available were written a long time ago and expose too much
low-level detail (imho) that will only embarass you. The Git Community Book
is really refreshing because it really deals with the most relevant things
for typical developers without dumbing down things.

Happy hacking.



2009/5/21 Tom Kacvinsky tkacvin...@mac.com

 Hi,

 I am looking at getting back into the FreeType project after a five or so
 year hiatus.  I see
 things have moved from cvs to git (skipped svn?)  Does anyone know of a
 good tutorial
 on git?

 Tom


 ___
 Freetype-devel mailing list
 Freetype-devel@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/freetype-devel

___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel

[ft-devel] git

[Tom Kacvinsky]

Hi,

I am looking at getting back into the FreeType project after a five  
or so year hiatus.  I see
things have moved from cvs to git (skipped svn?)  Does anyone know of  
a good tutorial

on git?

Tom


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: [ft-devel] git

[Ralph Giles]

On Thu, May 21, 2009 at 4:43 PM, Tom Kacvinsky tkacvin...@mac.com wrote:

 I am looking at getting back into the FreeType project after a five or so
 year hiatus.  I see
 things have moved from cvs to git (skipped svn?)  Does anyone know of a good
 tutorial on git?

http://git.or.cz/course/svn.html (-- git in terms of svn)
http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html

 -r


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel

[ft-devel] Git and ChangeLogs

[Huw Davies]

On Wed, Mar 25, 2009 at 03:37:13PM +0100, David Turner wrote:
 I also tried to apply your previous set of patches to the git repository,
 and it failed due to inconsistencies with the ChangeLog file. Can I ask you
 to provide a second set of patches from a more recent commit ?

For what it's worth, in Wine we don't submit patches that include a
ChangeLog diff.  The ChangeLog is updated automatically (from git log)
every time the maintainer makes a release.  This way we avoid
conflicts like the above.

Huw.


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel

[ft-devel] git problem solved

[Werner LEMBERG]

With the help of Johannes I was able to solve the problem with
modifying git commit messages.  Before actually doing it (and
populating the currently empty git repositories on Savannah) I want to
represent the process which I use.

Please comment!  In a few days I'll then actually do the conversion.
Are there any other (scriptable) changes you would like to have
applied to the commit messages?


  1. Get (or synchronize) the CVS repository files:

   cd
   mkdir cvs
   cd cvs
   rsync -avz \
 rsync://cvs.sv.gnu.org/sources/freetype/freetype2/ \
 freetype2

  2. Add an `Authors' file to the `freetype2' directory (attached).

   cd
   cp Authors cvs/freetype2

  3. Call `parsecvs' and compress the git objects:

   cd
   cd cvs/freetype2
   find . -name '*,v' | parsecvs
   git gc

  4. Move the created `.git' directory to a different place and check
 out all files:

   cd
   mkdir git
   cd git
   mkdir freetype2
   mv ../cvs/freetype2/.git freetype2
   cd freetype2
   git checkout HEAD

  5. Generate files which contain empty commit messages, together with
 the affected changes -- this is what I wanted to do from the very
 beginning!

   cd
   cd git
   sh get-empty-logs freetype2

 The `get-empty-logs' script is attached.

  6. Edit the created commit message files.

  7. Apply the modified commit message files to the git repository:

   cd
   cd git
   sh regenerate-git freetype2

 The `regenerate-git' script is attached.


   Werner
antoineL=Antoine Leca antoine-freet...@leca-marti.org
davidT=David Turner da...@freetype.org
erico=Eric Olson eric.ol...@sympatico.ca
freetype=David Turner da...@freetype.org
gasher=Graham Asher graham.as...@btinternet.com
jclaudius=Jens Claudius jens.claud...@yahoo.com
jet=Yamato, Masatake (大和正武) j...@gyve.org
just=Just van Rossum j...@letterror.com
leonardr=Leonard Rosenthol leona...@pdfsages.com
mpsuzuki=Suzuki, Toshiya (鈴木俊哉) mpsuz...@hiroshima-u.ac.jp
olvaffe=Wu, Chia-I (吳佳一) olva...@gmail.com
otaylor=Owen Taylor otay...@redhat.com
Peak=Pavel Kaňkovský p...@argo.troja.mff.cuni.cz
robert=Robert Wilhelm robert.wilh...@gmx.net
tetisoft=Detlef Würkner tetis...@apg.lahn.de
tomk=Tom Kacvinsky tom.kacvin...@3ds.com
werner=Werner Lemberg w...@gnu.org
wl=Werner Lemberg w...@gnu.org
# get-empty-logs git repository
#
# From the given repository, this script exctracts commit messages named
#
#   *** empty message ***
#
# and stores them, together with the corresponding diff, in the current
# directory in files of the form
#
#   commit date commit hash.txt
#
# The idea is that you modify the messages to something more meaningful.
# Note that everything below (and including) the `snip here' line won't
# be part of the commit message.
#
# After finishing you should call the `regenerate-git' script to apply the
# updated commit messages.

export PATH=/home/wl/git/git.compiled:$PATH
export TRASH_OFF=YES

currdir=`pwd`
cd $1

git log --pretty='format:%ci %H' \
--grep='\*\*\* empty log message \*\*\*' \
| sed 's/ +//' \
| while read filename; do
git show --pretty=format:'%s%n%n--- snip here ---%n%b' \
`echo $filename | sed 's/^.* //'` \
 $currdir/$filename.txt
  done

# eof
# regenerate-git git repository
#
# This script applies commit messages in files named
#
#   commit date commit hash.txt
#
# (as created by the `get-empty-logs' script, for example) to the given git
# repository; the files are expected to be in the current directory.
#
# The idea is that all git objects are checked whether a file name's commit
# date and commit hash is identical to a git object's commit date and
# commit hash, respectively.  If true, the file's contents down to the `snip
# here' line (which isn't included) is used as a new commit message.

export PATH=/home/wl/git/git.compiled:$PATH
export TRASH_OFF=YES

export currdir=`pwd`
cd $1

git filter-branch \
  --env-filter 'FILENAME=`git show -s --pretty=format:%ci %H $GIT_COMMIT \
  | sed s/ +//`
export FILENAME' \
  --tag-name-filter cat \
  --msg-filter 'if test -f $currdir/$FILENAME.txt; then
  cat $currdir/$FILENAME.txt \
  | sed /--- snip here ---/,\$d;
else
  cat;
fi'

# eof
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel