# ChangeLog for app-crypt/johntheripper # Copyright 2002-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/app-crypt/johntheripper/ChangeLog,v 1.10 2003/10/01 19:50:48 taviso Exp $ 01 Oct 2003; Tavis Ormandy johntheripper-1.6.ebuild: Stable on alpha 13 Feb 2003; Guy Martin johntheripper-1.6.ebuild : Changed keyword ~hppa to hppa. *johntheripper-1.6-r1 (13 Feb 2003) 13 Feb 2003; johntheripper-1.6-r1.ebuild files/digest-johntheripper-1.6-r1 : new version that uses patches for ntlm, mysql, etc password cracking 13 Feb 2003; johntheripper-1.6-r1.ebuild files/digest-johntheripper-1.6-r1 : new *johntheripper-1.6 (22 May 2002) 28 Mar 2003; Pieter Van den Abeele johntheripper-1.6.ebuild : Moved to stable ppc 09 Feb 2003; Seemant Kulleen johntheripper-1.6.ebuild : Changed to use epatch. Also, changed sed expression delimiters from / to :, closing bug #15006 by Blu3 06 Dec 2002; Rodney Rees : changed sparc ~sparc keywords 22 May 2002; Grant Goodyear New package. I use the debian patch because it contains some useful hacks to make john fit in an LFS filesystem (not to mention man pages). -- Explanation of ChangeLog format: Every new version or revision of the package should be marked by a '*' seperator line as above. Changes since the last revision have to be added to the top of the file, underneath the initial copyright and cvs header comments, in exactly the same format as this comment. This means that you start with header line that has the following format, indented two spaces: DD MMM YYYY; your_name changed_file1, changed_file2: Your explanation should follow. It should be indented and wrapped at a line width of 80 characters. The changed_files can be omitted if they are obvious; for example, if you are only modifying the .ebuild file and committing a new rev of a package. Any details about what exactly changed in the code should be added as a message when the changes are committed to cvs, not in this file.