summaryrefslogtreecommitdiff
path: root/set-serial.sh
Commit message (Collapse)AuthorAgeFilesLines
* Deal with changed git-log behavior in version 1.9.x.Peter Simons2014-02-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The latest version of git-log tracks the origin of a given file through sub-module commits. The macro AX_ABSOLUTE_HEADER, for instance, used to have 6 commits attributed to it, but now it has 26: $ git log --oneline -- m4/ax_absolute_header.m4 27948f4 ALL: update web site URL to http://www.gnu.org/software/autoconf-archive/MACRO-NAME.html c6b6f51 Assigned all macros a unique serial number. 89b80e0 Augmented the text of the all-permissive license by an express warranty disclaimer. d722dcd Add AU_ALIAS calls to new files for all recently renamed macros. 6fc99d3 Center the URL at the top of every file and use consistent word-wrapping. acffb06 Rename gl_TRILINOS_ABSOLUTE_HEADER to AX_ABSOLUTE_HEADER. 054e8ad remove m4 submodule fa1b1bb m4: update reference to macro branch 548839e m4: update reference to macro branch d9afb8a m4: update reference to macro branch 8968e9d m4: update reference to macro branch 862b513 Avoid non-ASCII characters in m4 files. d7160b6 m4: update reference to macro branch 9062013 m4: update reference to macro branch 3cf85b5 m4: update reference to macro branch 49af2e9 m4: update reference to macro branch 950f2a7 m4: update reference to macro branch c610f41 m4: update reference to macro branch 78d7777 m4: update reference to macro branch ddd0b53 m4: update reference to macro branch fcb87e1 m4: update reference to macro branch 702ea3c m4: update reference to macro branch cee9eea m4: update reference to macro branch e3df236 m4: update reference to macro branch 3c89e38 m4: update reference to macro branch 3b30002 maint: added initial version of the toolchain This new behavior means that most of our macros suddenly experience large bumps in their #serial number for no apparent reason. To prevent this situation, we limit the version history git-log may consider to 054e8ad..HEAD, i.e. all commits prior to the sub-module merge don't count. This gives us the old behavior of git-log back.
* In our internal bash scripts, the interpreter is now run through ↵Peter Simons2013-02-061-1/+1
| | | | /usr/bin/env instead of having it's location hard-coded at /bin/bash.
* set-serial.sh: make more portable, faster and safer.Diego Elio Pettenò2010-12-181-5/+5
| | | | | | | | | | | POSIX sh disallows dashes in function names, so rename the function to set_serial_number. Check for staged changes as well as non-staged once to see if the revision has to be increased further. Call set_serial_number just once in all cases, rather than calling it twice if there are both new revisions and scheduled changes.
* Implement a TODO item: add set-serial to build process (and fix a comment ↵Reuben Thomas2010-12-081-1/+1
| | | | typo in set-serial.sh).
* set-serial.sh: fixed for use with Git 1.7.0Peter Simons2010-02-231-1/+1
| | | | | Apparently, git status no longer returns a non-zero exit code in case the file had been modified. Instead, git diff --exit-code can be used.
* set-serial.sh: use "git log --oneline" to determine the number of revision ↵Peter Simons2010-01-121-1/+1
| | | | | | | for a macro This seems to be more reliable (and easier) than the previous 'grep -c' approach.
* set-serial.sh: generate serial numbers automaticallyPeter Simons2009-12-251-0/+25
Usage: ./set-serial.sh m4/ax_foo.m4 m4/ax_bar.m4 [...] This script determines the number of revisions that have occurred to a given m4 file, and patches an appropriate #serial number into the file automatically. After that, the script checks whether git(1) regards that file as modified now. If it does, the serial number is bumped one more time to ensure that the number will be correct as soon as the changes have been committed. Consequently, running this script on an unmodified m4 file with correct serial number information is a no-op and doesn't change anything.
View Lorry Controller Status