grep-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

grep branch, master, updated. v2.25-33-ge9ee68d


From: Paul Eggert
Subject: grep branch, master, updated. v2.25-33-ge9ee68d
Date: Fri, 15 Jul 2016 10:02:35 +0000 (UTC)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "grep".

The branch, master has been updated
       via  e9ee68dfd8150145a64ec11e5227c9029c7ee3c0 (commit)
       via  65fa1e31c0da8dc26f872c050e81b649dc65a32b (commit)
       via  cf39d76da476b747b1b875bdd92dd00770ae4936 (commit)
      from  220cbd1c8459b9e0d284d62aa65023c663bb71f8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.savannah.gnu.org/cgit/grep.git/commit/?id=e9ee68dfd8150145a64ec11e5227c9029c7ee3c0


commit e9ee68dfd8150145a64ec11e5227c9029c7ee3c0
Author: Paul Eggert <address@hidden>
Date:   Fri Jul 15 12:02:01 2016 +0200

    maint: modernize HACKING a bit
    
    * HACKING: Remove some ancient history to simplify maintenance.

diff --git a/HACKING b/HACKING
index a4ab327..111870c 100644
--- a/HACKING
+++ b/HACKING
@@ -3,14 +3,6 @@ Grep Contribution Guidelines
 
 Prerequisites
 =============
-You will need the "git" version control tools.
-On Fedora-based systems, do "yum install git".
-On Debian-based ones install the "git-core" package.
-Then run "git --version".  If that says it's older than
-version 1.4.4, then you'd do well to get a newer version.
-At worst, just download the latest stable release from
-http://git.or.cz/ and build from source.
-
 For details on building the programs in this package, see
 the file, README-hacking.
 
@@ -22,12 +14,9 @@ You can get a copy of the latest with this command:
 
     git clone git://git.sv.gnu.org/grep
 
-That downloads the entire repository, including revision control history
-dating back to 1991.  The repository (the part you download, and which
-resides in grep/.git) currently weighs in at about 9MB.  So you don't
-want to download it more often than necessary.  Once downloaded, you
-can get incremental updates by running one of these commands from
-inside your new grep/ directory:
+That downloads the entire repository, including revision control history.
+Once downloaded, you can get incremental updates by running one of
+these commands from inside your new grep/ directory:
 
 If you have made *no* changes:
     git pull
@@ -202,11 +191,10 @@ grep-specific:
 
 No more ChangeLog files
 =======================
-Do not modify any of the ChangeLog files in grep.  Starting in
-2008, the policy changed.  Before, we would insert the exact same text
-(or worse, sometimes slightly differing) into both the ChangeLog file
-and the commit log.  Now we put that information only in the commit log,
-and generate the top-level ChangeLog file from logs at "make dist" time.
+
+Do not modify any the ChangeLog files during development.  Instead,
+put that information only in commit messages.  The "make dist" command
+will generate the top-level ChangeLog file from commit messages.
 As such, there are strict requirements on the form of the commit log
 messages.
 

http://git.savannah.gnu.org/cgit/grep.git/commit/?id=65fa1e31c0da8dc26f872c050e81b649dc65a32b


commit e9ee68dfd8150145a64ec11e5227c9029c7ee3c0
Author: Paul Eggert <address@hidden>
Date:   Fri Jul 15 12:02:01 2016 +0200

    maint: modernize HACKING a bit
    
    * HACKING: Remove some ancient history to simplify maintenance.

diff --git a/HACKING b/HACKING
index a4ab327..111870c 100644
--- a/HACKING
+++ b/HACKING
@@ -3,14 +3,6 @@ Grep Contribution Guidelines
 
 Prerequisites
 =============
-You will need the "git" version control tools.
-On Fedora-based systems, do "yum install git".
-On Debian-based ones install the "git-core" package.
-Then run "git --version".  If that says it's older than
-version 1.4.4, then you'd do well to get a newer version.
-At worst, just download the latest stable release from
-http://git.or.cz/ and build from source.
-
 For details on building the programs in this package, see
 the file, README-hacking.
 
@@ -22,12 +14,9 @@ You can get a copy of the latest with this command:
 
     git clone git://git.sv.gnu.org/grep
 
-That downloads the entire repository, including revision control history
-dating back to 1991.  The repository (the part you download, and which
-resides in grep/.git) currently weighs in at about 9MB.  So you don't
-want to download it more often than necessary.  Once downloaded, you
-can get incremental updates by running one of these commands from
-inside your new grep/ directory:
+That downloads the entire repository, including revision control history.
+Once downloaded, you can get incremental updates by running one of
+these commands from inside your new grep/ directory:
 
 If you have made *no* changes:
     git pull
@@ -202,11 +191,10 @@ grep-specific:
 
 No more ChangeLog files
 =======================
-Do not modify any of the ChangeLog files in grep.  Starting in
-2008, the policy changed.  Before, we would insert the exact same text
-(or worse, sometimes slightly differing) into both the ChangeLog file
-and the commit log.  Now we put that information only in the commit log,
-and generate the top-level ChangeLog file from logs at "make dist" time.
+
+Do not modify any the ChangeLog files during development.  Instead,
+put that information only in commit messages.  The "make dist" command
+will generate the top-level ChangeLog file from commit messages.
 As such, there are strict requirements on the form of the commit log
 messages.
 

http://git.savannah.gnu.org/cgit/grep.git/commit/?id=cf39d76da476b747b1b875bdd92dd00770ae4936


commit e9ee68dfd8150145a64ec11e5227c9029c7ee3c0
Author: Paul Eggert <address@hidden>
Date:   Fri Jul 15 12:02:01 2016 +0200

    maint: modernize HACKING a bit
    
    * HACKING: Remove some ancient history to simplify maintenance.

diff --git a/HACKING b/HACKING
index a4ab327..111870c 100644
--- a/HACKING
+++ b/HACKING
@@ -3,14 +3,6 @@ Grep Contribution Guidelines
 
 Prerequisites
 =============
-You will need the "git" version control tools.
-On Fedora-based systems, do "yum install git".
-On Debian-based ones install the "git-core" package.
-Then run "git --version".  If that says it's older than
-version 1.4.4, then you'd do well to get a newer version.
-At worst, just download the latest stable release from
-http://git.or.cz/ and build from source.
-
 For details on building the programs in this package, see
 the file, README-hacking.
 
@@ -22,12 +14,9 @@ You can get a copy of the latest with this command:
 
     git clone git://git.sv.gnu.org/grep
 
-That downloads the entire repository, including revision control history
-dating back to 1991.  The repository (the part you download, and which
-resides in grep/.git) currently weighs in at about 9MB.  So you don't
-want to download it more often than necessary.  Once downloaded, you
-can get incremental updates by running one of these commands from
-inside your new grep/ directory:
+That downloads the entire repository, including revision control history.
+Once downloaded, you can get incremental updates by running one of
+these commands from inside your new grep/ directory:
 
 If you have made *no* changes:
     git pull
@@ -202,11 +191,10 @@ grep-specific:
 
 No more ChangeLog files
 =======================
-Do not modify any of the ChangeLog files in grep.  Starting in
-2008, the policy changed.  Before, we would insert the exact same text
-(or worse, sometimes slightly differing) into both the ChangeLog file
-and the commit log.  Now we put that information only in the commit log,
-and generate the top-level ChangeLog file from logs at "make dist" time.
+
+Do not modify any the ChangeLog files during development.  Instead,
+put that information only in commit messages.  The "make dist" command
+will generate the top-level ChangeLog file from commit messages.
 As such, there are strict requirements on the form of the commit log
 messages.
 

-----------------------------------------------------------------------

Summary of changes:
 HACKING                       |   26 +++++++-------------------
 src/kwset.c                   |    5 +++--
 tests/Makefile.am             |    1 +
 tests/{c-locale => two-chars} |   20 +++++++++-----------
 4 files changed, 20 insertions(+), 32 deletions(-)
 copy tests/{c-locale => two-chars} (53%)


hooks/post-receive
-- 
grep



reply via email to

[Prev in Thread] Current Thread [Next in Thread]