git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@inai.de>
To: "Ralph Haußmann" <ralph@scanmyfood.de>
Cc: "'Thomas Rast'" <trast@inf.ethz.ch>,
	"'Ralf Thielow'" <ralf.thielow@gmail.com>,
	"'Christian Stimming'" <stimming@tuhh.de>,
	"'Sven Fuchs'" <svenfuchs@artweb-design.de>,
	git@vger.kernel.org, "'Jan Krüger'" <jk@jk.gs>
Subject: Re: AW: English/German terminology, git.git's de.po, and pro-git
Date: Mon, 13 May 2013 21:25:23 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1305132119220.2288@nerf07.vanv.qr> (raw)
In-Reply-To: <001d01ce500b$c7c08b70$5741a250$@scanmyfood.de>


On Monday 2013-05-13 20:57, Ralph Haußmann wrote:
>
>There is a glossary for the pro-git book (see [2]) but it is not up-to-date 
>and it is also mixed. Therefor I would like to avoid using this glossary. 
>I like the idea of a shared wiki (git de.po and pro-git). 
>I suggest a single page as overview and single pages for 
>complicated terms. Maybe we can use our GitHub wiki (see also [3]).
>
>[2] https://github.com/progit/progit/blob/master/de/NOTES
>[3] https://github.com/progit-de/progit/wiki/Glossar

This is how I envision a good glossary

	http://inai.de/files/git-glossary.txt

Maybe the "Benevolent Dictator" model might be better suited
instead of a wiki? (Think of the edit wars.)

  reply	other threads:[~2013-05-13 19:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 12:54 English/German terminology, git.git's de.po, and pro-git Thomas Rast
2013-05-13 13:57 ` Jan Engelhardt
2013-05-13 17:19   ` Jens Lehmann
2013-05-13 18:57   ` AW: " Ralph Haußmann
2013-05-13 19:25     ` Jan Engelhardt [this message]
2013-05-14 17:51       ` Ralf Thielow
2013-05-15 10:23         ` Holger Hellmuth (IKS)
2013-05-15 11:26           ` Jens Lehmann
2013-05-15 11:56             ` Jan Engelhardt
2013-05-15 12:27               ` Jens Lehmann
2013-05-15 13:14                 ` Jan Engelhardt
2013-05-15 15:31                   ` Holger Hellmuth (IKS)
2013-05-15 17:28                     ` Jan Engelhardt
2013-05-16  5:57             ` Ralf Thielow
2013-05-16  8:48               ` Holger Hellmuth (IKS)
2013-05-19 16:06                 ` Ralf Thielow
2013-05-19 16:56                 ` Ralf Thielow
2013-05-20  4:01                   ` Holger Hellmuth
2013-05-22 14:09                     ` Ralf Thielow
2013-05-16  9:00               ` Thomas Rast
2013-05-19 16:49                 ` Ralf Thielow
2013-05-19 16:53               ` Ralf Thielow
2013-05-20 19:41                 ` Christian Stimming
2013-05-22 15:16                   ` Ralf Thielow
2013-05-22 15:52                     ` Holger Hellmuth (IKS)
2013-05-22 16:43                       ` Jan Engelhardt
2013-05-23 18:16                     ` Bernhard R. Link
2013-05-24 16:41                       ` Ralf Thielow
2013-06-16 21:22                       ` Jan Engelhardt
2013-05-24 16:51                 ` Ralf Thielow
2013-05-13 16:30 ` Ralf Thielow
2013-05-16 10:49 ` Christian Stimming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.01.1305132119220.2288@nerf07.vanv.qr \
    --to=jengelh@inai.de \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=ralf.thielow@gmail.com \
    --cc=ralph@scanmyfood.de \
    --cc=stimming@tuhh.de \
    --cc=svenfuchs@artweb-design.de \
    --cc=trast@inf.ethz.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).