public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/emacs:master commit in: /
Date: Tue, 26 Jan 2016 22:46:50 +0000 (UTC)	[thread overview]
Message-ID: <1453848366.4561cb2152fc5ba6b243664f4ebcf78142832b79.ulm@gentoo> (raw)

commit:     4561cb2152fc5ba6b243664f4ebcf78142832b79
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 26 18:42:15 2016 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Jan 26 22:46:06 2016 +0000
URL:        https://gitweb.gentoo.org/proj/emacs.git/commit/?id=4561cb21

skel.ChangeLog: Sync from portage tree.

 skel.ChangeLog | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/skel.ChangeLog b/skel.ChangeLog
index f8c5983..10ffc31 100644
--- a/skel.ChangeLog
+++ b/skel.ChangeLog
@@ -1,5 +1,5 @@
 # ChangeLog for <CATEGORY>/<PACKAGE_NAME>
-# Copyright 1999-2014 Gentoo Foundation; Distributed under the GPL v2
+# Copyright 1999-2016 Gentoo Foundation; Distributed under the GPL v2
 # $Id$
 
 *<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
@@ -39,9 +39,9 @@
 
   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
+  added to our Git 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
+  initial copyright and file 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" "*"
@@ -55,7 +55,7 @@
   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.
+  added as a message when the changes are committed to Git, not in this file.
 
 -- A word regarding credit:
 


             reply	other threads:[~2016-01-26 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 22:46 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-26 18:42 [gentoo-commits] proj/emacs:master commit in: / Ulrich Müller
2014-01-19 17:07 Ulrich Müller
2013-07-12 21:16 Mats Lidell

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=1453848366.4561cb2152fc5ba6b243664f4ebcf78142832b79.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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