From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2071D1386F4 for ; Sun, 9 Aug 2015 08:33:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 583C5E0833; Sun, 9 Aug 2015 08:33:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C69ABE081C for ; Sun, 9 Aug 2015 08:33:28 +0000 (UTC) Received: from oystercatcher.gentoo.org (unknown [IPv6:2a01:4f8:202:4333:225:90ff:fed9:fc84]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 958C3340A30 for ; Sun, 9 Aug 2015 08:33:26 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id D60AF146 for ; Sun, 9 Aug 2015 08:33:24 +0000 (UTC) From: "James Le Cuirot" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "James Le Cuirot" Message-ID: <1439081363.93dcdc4b6aaf104aba42fabd945915f5b8e77fc4.chewi@gentoo> Subject: [gentoo-commits] proj/java:master commit in: / X-VCS-Repository: proj/java X-VCS-Files: skel.ChangeLog X-VCS-Directories: / X-VCS-Committer: chewi X-VCS-Committer-Name: James Le Cuirot X-VCS-Revision: 93dcdc4b6aaf104aba42fabd945915f5b8e77fc4 X-VCS-Branch: master Date: Sun, 9 Aug 2015 08:33:24 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Archives-Salt: 29195022-2524-436c-b466-701d9db7e04b X-Archives-Hash: ff7d3a6b46686cdd8f87d25bdb22848b commit: 93dcdc4b6aaf104aba42fabd945915f5b8e77fc4 Author: Andreas Sturmlechner gmail com> AuthorDate: Sun Aug 9 00:49:23 2015 +0000 Commit: James Le Cuirot gentoo org> CommitDate: Sun Aug 9 00:49:23 2015 +0000 URL: https://gitweb.gentoo.org/proj/java.git/commit/?id=93dcdc4b Delete skel.ChangeLog Package-Manager: portage-2.2.20 skel.ChangeLog | 67 ---------------------------------------------------------- 1 file changed, 67 deletions(-) diff --git a/skel.ChangeLog b/skel.ChangeLog deleted file mode 100644 index fa1414a..0000000 --- a/skel.ChangeLog +++ /dev/null @@ -1,67 +0,0 @@ -# ChangeLog for / -# Copyright 1999-2007 Gentoo Foundation; Distributed under the GPL v2 -# $Header: $ - -*-- (DD MMM YYYY) - - DD MMM YYYY; YOUR_NAME changed_file1, changed_file2 : - Initial import. Ebuild submitted by submitter_name . - Note that the "changed_file" listing is optional if you are simply bumping - the rev of the ebuild and are only making changes to the .ebuild file - itself. Also note that we now have a single unified paragraph rather than - having the first line separated from the rest by a newline. Everything - should be in one block like this. (note by drobbins, 16 Jul 2002) - - DD MMM YYYY; YOUR_NAME changed_file1, changed_file2: this is - an earlier ChangeLog entry. - --- Explanation of ChangeLog format: - - *************************************************************************** - THIS IS IMPORTANT: The ChangeLog format is a *chronological* account of all - changes made to a set of ebuilds. That means that the most recent ChangeLog - entry *always* goes at the top of the file. More explanation below. - *************************************************************************** - - *************************************************************************** - ANOTHER IMPORTANT NOTE: There are some ChangeLogs that don't follow this - format and organize all changes under the "correct" "*" entry. This is not - correct. However, rather than making a concerted effort to fix these - ChangeLogs, we should spend our energy defining a comprehensive and strict - XML-based ChangeLog format which we then migrate to. But for any entries to - any ChangeLog that *you* make, please make sure to always add entries to the - top of the file like a good boy/girl. Even do this if it's clear that you're - adding an entry to a b0rked ChangeLog. - *************************************************************************** - - This changelog is targeted to users. This means that the comments should be - well explained and written in clean English. - - Every new version or revision of the package should be marked by a '*' - separator line as above to indicate where in the chronology it was first - added to our CVS tree. Any changes since the last revision, really _any - changes at all_ 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. If you are modifying older ebuilds, simply note them as changed - files and add your entry to the top of the ChangeLog. Resist the temptation - to "organize" your ChangeLog entries by placing them under the "correct" "*" - entries -- this isn't the purpose of the "*" entries. - - 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. - --- A word regarding credit: - - Please add credit information ("ebuild submitted by ...", "patch submitted - by ...") to the ChangeLog. Do not add this information to the ebuilds - themselves. - - And remember: Give credit where credit is due. We're all doing this for - free, so the best we can hope (and expect!) to receive is credit.