gparted/HACKING
Mike Fleetwood 4b8d4be789 Remove unallocated space comment from HACKING file (!50)
The HACKING file should be hints for making changes to the code base and
associated processes.  A overview of how GParted handled unallocated
space was not that.  Also now the size of a JFS is accurately calculated
using JFS as an example of a file system with intrinsic unallocated
space is no longer valid.  Therefore removed from the HACKING file.
Instead add the original commit message as an extended comment to method
calc_significant_unallocated_sectors().

Closes !50 - Calculate JFS size accurately
2019-11-14 17:12:06 +00:00

32 lines
1,012 B
Plaintext

git guidelines for gparted
==========================
Please do not commit directly to the git.gnome.org/gparted repository
unless you have been given the green light to commit freely to
gparted. When in doubt assume you haven't ;-).
If you are a translator feel free to mark strings for translation, fix
typos in the code, etc. I'd appreciate it if you would notify me of
anything you've done.
Please send patches for build & configure fixes too. I really appreciate
your help, I just want to review these fixes before applying.
!!WHENEVER YOU COMMIT, PLACE A COMMENT IN GIT!!
even when it's only one character. =)
Thanks,
Curtis
Translatable files
==================
The file po/POTFILES.in lists all source files which do or could contain
translatable strings. Remember to update when adding new and removing
old source code files include/*.h and src/*.cc. Generally .cc files are
included and .h files are not, but there are exceptions. Some mistakes
can be detected using:
make distcheck