aniani/elinks
1
0
Fork 0
mirror of https://github.com/rkd77/elinks.git synced 2024-12-04 14:46:47 -05:00
Code

doc: We're using Git rather than CVS.

Browse Source
This commit is contained in:
Kalle Olavi Niemitalo 2009-03-24 07:20:40 +02:00 committed by Kalle Olavi Niemitalo
parent 58b5e3968f
commit 255cbf6ae0
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/hacking.txt
View File

@ -661,7 +661,7 @@ diff -ru elinks/ elinks+mysuperfeature/ >elinks-mysuperfeature.patch
Please manually remove any bloat like changes in ./configure, whitespace Please manually remove any bloat like changes in ./configure, whitespace
changes etc. ;-). changes etc. ;-).
We also accept output from `cvs diff -u` :). The statement about bloat We also accept output from `git diff` :). The statement about bloat
removing above still applies. removing above still applies.
Big patches are hard to review so if your feature involves a lot of changes Big patches are hard to review so if your feature involves a lot of changes

4
po/README
View File

@ -107,7 +107,7 @@ reasonable editor.
In order to compile, get warnings and actually use your updated language file In order to compile, get warnings and actually use your updated language file
you will however need the gettext tools. If you don't have any of these tools you will however need the gettext tools. If you don't have any of these tools
please don't hesitate to still do the update and send it to the mailinglist or please don't hesitate to still do the update and send it to the mailinglist or
bugzilla so it can be added to CVS. By next release or nightly generated tarball bugzilla so it can be added to Git. By next release or nightly generated tarball
you can then make use of your updates. you can then make use of your updates.
2.2 The basics of updating: 2.2 The basics of updating:
@ -185,7 +185,7 @@ translation for each plural form.
2.3 Synchronizing .po files with the code 2.3 Synchronizing .po files with the code
----------------------------------------- -----------------------------------------
IMPORTANT: if you changed strings in the code, or if you're using a cvs version IMPORTANT: if you changed strings in the code, or if you're using a Git version
of ELinks, take care of synchronization between code and po files. Before any of ELinks, take care of synchronization between code and po files. Before any
change to a po file, you must synchronize it with code. change to a po file, you must synchronize it with code.