summaryrefslogtreecommitdiffstats
path: root/tools
AgeCommit message (Collapse)AuthorFilesLines
2013-09-27tools: Remove Drupal/SourceForge scriptsHolger Weiss9-497/+0
We moved our web site away from Drupal and the snapshots/guidelines away from SourceForge. The new infrastructure scripts will be maintained in a separate repository together with the Markdown source of the new web site.
2013-09-27Remove tools/git2svn.plHolger Weiss1-129/+0
We no longer mirror out Git repositories into Subversion.
2013-08-30Merge branch 'hw/update-pm'Holger Weiss1-64/+250
* hw/update-pm: Use own variable instead of ENV Updated with last working copy of build_perl_modules used by Opsview Conflicts: tools/build_perl_modules
2013-08-23Use own variable instead of ENVTon Voon1-1/+1
2013-08-23Updated with last working copy of build_perl_modules used by OpsviewTon Voon1-63/+249
2013-08-23perlmods: fixed install_orderSven Nierlein1-0/+1
on older systems Module::Build is not available by default, therefore we have to change the order of installation.
2013-08-20Updated perl modulesTon Voon1-1/+1
2013-08-20Update the bundled Params::Validate moduleHolger Weiss1-4/+19
Building the old version fails with recent Perl releases: | Validate.xs: In function `get_type': | Validate.xs:208:5: error: duplicate case value | Validate.xs:205:5: error: previously used here
2012-11-07Fix sfwebcron probe fileThomas Guyot-Sionnest1-7/+6
The initial file was created in the user's home and later tested in the doc directory. Instead, just rsync if the file is missing. Also add some temporary files to gitignore/make clean
2012-11-03Update toolsdermoth2-80/+12
- fix sfwebcron (tool updating sf developer guidelines) - remove obsolete snapshot script
2012-11-03Add scripts that update man pages in drupaldermoth2-0/+45
2011-01-01Update the README textThomas Guyot-Sionnest1-3/+4
2010-10-12sfsnapshotgit: Better handling of remote refsThomas Guyot-Sionnest1-4/+10
This commit allow to track branches from unusually-named remote refs and makes possible using external remotes (other than origin) for snapshots.
2010-07-14Added text re: MD5SUM updates in nightlies, but tarballs notTon Voon1-0/+3
2010-07-02git-notify: Be careful with "--no-merge"Holger Weiss1-5/+6
The "-X" option (which asks git-notify to not report merge commits) was implemented by setting the "--no-merge" option on each invocation of git-rev-list(1). However, we do not only use git-rev-list(1) to get the list of new commits, but also to check whether the old branch head (or tag) is a parent of the new branch head (or tag). For this latter check, the "--no-merge" option should not be set; otherwise, git-notify would be fooled to believe that the branch has been rewritten if the old head was a merge commit.
2010-04-28tools/distclean: use git-clean when possibleThomas Guyot-Sionnest1-0/+12
git-clean is much faster and more reliable... Also add confdefs.h in gitignore, although this file is normally removed at the end of the configure script.
2010-04-14git-notify: Fix the ordering of commitsHolger Weiss1-1/+1
If notifications for multiple commits are created, sort them chronologically instead of in reverse chronological order.
2010-04-13Sync with the latest Gnulib code (177f525)Thomas Guyot-Sionnest1-0/+4
Signed-off-by: Thomas Guyot-Sionnest <dermoth@aei.ca>
2009-12-07git-notify: Pipe e-mails directly to sendmail(8)Holger Weiss2-22/+8
Use sendmail(8) instead of mail(1) in order to be able to set the "Content-Type" header field on systems where the available mail(1) command doesn't allow for setting it. This makes the "-H" flag (cf. commit 71350c5a) unnecessary.
2009-12-06Enable CIA's commit notificationsHolger Weiss2-2/+4
We now use CIA's service to send commit notifications to IRC. They are currently sent to the #Nagios-Devel channel on Freenode. See: http://cia.vc/stats/project/nagiosplug/ http://cia.vc/account/bots/15699/
2009-11-19Updated link to sfsnapshotgitTon Voon1-1/+1
2009-11-11Fix fetching of remote branchesThomas Guyot-Sionnest1-1/+1
2009-11-11Many fixes to snapshot scriptsdermoth2-22/+43
sfsnapshotgit: - Use fetch/reset instead to pull to avoid merges on forced updates sfsnapshot-upload: - Fix link deletion walking the entire home dir - Allow CLEAN_TIME=0 (no retention) - Re-add per-branch links when CLEAN_TIME > 0 - Add many comments
2009-11-07Git commit notifications via post-receive hookHolger Weiss2-94/+23
Now that we moved our Git repositories to SourceForge, we don't need to maintain local clones for generating commit notifications anymore, as SourceForge provides shell access to the repositories. Instead, we now run git-notify as a post-receive hook on the SourceForge server. Actually, we use a wrapper which executes git-notify with the desired options and which makes it easy to add other post-receive hooks in the future.
2009-11-07git-notify: Support SourceForge repositoriesHolger Weiss1-6/+14
The Gitweb URLs for repositories hosted by SourceForge are slightly different than other Gitweb URLs. The correct URL cannot be specified via "-u" if we append "/$repos_name.git/?" to that URL as we usually do. If the new "-S" flag is specified or "notify.sourceforge" is set, we'll append "/$repos_name;" instead, which makes the "-u" option usable for SourceForge repositories.
2009-11-07git-notify: Optionally call mail(1) without "-a"Holger Weiss1-1/+13
Not all mail(1) implementations support specifying additional header fields via "-a": with some, this flag is used for attaching files, others don't provide an "-a" flag at all (this is true for the /bin/mail utility currently installed on the SourceForge servers, for example). We now provide the "-H" flag and the "notify.legacyMail" configuration key for these cases.
2009-11-07git-notify: Polish up the "tag notifications"Holger Weiss1-2/+2
Use better labels for the tag ref and the SHA1 name of the tag object.
2009-11-07git-notify: Distinguish between tag typesHolger Weiss1-5/+24
Distinguish between annotated tags and lightweight tags. In the former case, send an annotated "tag notification", in the latter case, send a "ref change notification" (as we did in both cases before).
2009-11-07git-notify: Fix "global" notificationsHolger Weiss1-1/+4
If the number of commits included with a single push exceeds the maximum specified via "-n", a single notification will be generated instead of individual e-mails. For listing the commits within such a notification, git-rev-list(1)'s "--pretty" option is used. This yields output which the git_rev_list() subroutine didn't accept. That's now fixed.
2009-11-07git-notify: Optionally [tag] the subjectHolger Weiss1-0/+9
If the new "-T" option is specified or "notify.emitRepository" is set, the subject of e-mail notifications will be prefixed with [<tag>], where <tag> is the name of the updated repository.
2009-11-07git-notify: Optionally omit the author nameHolger Weiss1-3/+10
If the new "-A" option is specified (or "notify.omitAuthor" is set), the author name will be omitted from the subject of e-mail notifications.
2009-11-07git-notify: Make abbreviating Gitweb URLs optionalHolger Weiss1-9/+17
The SHA1 object name part of Gitweb URLs is now only shortened if the user requested this by specifying the new "-z" option (or by setting "notify.shortURLs"). While at it, also shorten the additional URL which references a diff in e-mail notifications which don't include that diff inline because its size exceeds the maximum number of bytes specified via "-s". Note that while the abbreviated SHA1 object names will be unique at push time, this cannot be guaranteed for the future, so the shortened URLs might break some day.
2009-11-07git-notify: Make showing the committer optionalHolger Weiss1-1/+7
Only the author's name and address will now be mentioned in a commit notification by default. However, if the "-C" option is specified (or "notify.showCommitter" is set), the committer's name and address will also be included in the notification if the committer is not the author of the commit (as we previously did by default).
2009-11-07git-notify: Make using a state file optionalHolger Weiss1-7/+7
Making use of a state file in order to prevent duplicate notifications is now optional. The user must explicitly specify a file path via the "-t" option or by setting the git-config(1) variable "notify.statefile" to activate this functionality.
2009-11-07git-notify: Don't abort if mail(1) exits non-zeroHolger Weiss1-1/+1
As nothing in git-notify depends on the success of the mail(1) call, don't abort if it fails, just spit out a warning.
2009-11-07git-notify: Drop the $sent_notices variableHolger Weiss1-8/+2
Now that we don't ignore empty commits anymore, there's no need to keep track of the number of commits actually notified about, as that will always be equal to the number of commits returned by get_new_commits().
2009-11-07Revert "git-notify: Ignore `empty' commits"Holger Weiss1-6/+4
This reverts commit db63fbfa036f5cd757aedf4547fef9e195a8c285, as it is no longer needed and we'd like to keep the diff against the git-notify version maintained by the Wine people as small as possible. The purpose of db63fbfa was to suppress notifications on empty merge commits, which can now be requested directly by specifying git-notify's "-X" option. (Our change was implemented before the "-X" option was available, even though the Git history suggests otherwise.) Conflicts: tools/git-notify
2009-11-07Revert "git-notify: Remove unused [...] code"Holger Weiss1-33/+68
This reverts commit 5445b9769f254781e482062bacc6603a5cd63059. Alexandre Julliard pointed out that the code in question was used if git-notify was explicitly called with the SHA1 name of an annotated tag object. At the moment, the code in question actually _is_ unused due to later modifications, but it wasn't at the time 5445b976 was committed, and we'll add further changes so that the code will be used again in the future. Conflicts: tools/git-notify
2009-11-06git-notify: Minor cosmetic changesHolger Weiss1-2/+3
Fix the description of the "-U" option.
2009-10-29Allow rsyncing to local pathsThomas Guyot-Sionnest1-1/+2
2009-10-29Add snapshots upload scriptsThomas Guyot-Sionnest1-0/+100
2009-10-26git-notify: Make the state file group writableHolger Weiss1-0/+7
For shared repositories, the state file used by git-notify should usually be group writable, so we now set the umask to 0002 by default. This can be adjusted by setting the "notify.umask" configuration key or by using the "-U" option on the command line.
2009-10-26git-notify: Remove an empty subroutineHolger Weiss1-5/+0
The gitweb_url() subroutine was an unused and empty hangover.
2009-10-25git-update-mirror: Remove a useless sed(1) callHolger Weiss1-1/+1
The sed(1) command in question was a hangover which had no effect anymore.
2009-10-24git-notify: Check the exit status of pipesHolger Weiss1-5/+5
Properly check the exit status of all processes we execute and abort on error.
2009-10-24git-notify: Handle non-UTF-8 commitsHolger Weiss1-5/+8
Make sure that commit messages which use an encoding other than US-ASCII or UTF-8 are handled correctly. Also, assume that the diff contents use the same encoding as the commit message. This assumption may well be wrong, but that's the best we can do.
2009-10-24git-notify: Don't generate duplicate notificationsHolger Weiss1-0/+61
Never notify on a given commit more than once, even if it's referenced via multiple branch heads. We make sure this won't happen simply by maintaining a list of commits we notified about. The file path used for saving this list can be specified using the new "-t" option. (The contrib/hooks/post-receive-email script distributed with Git tries hard to avoid such a list, but it doesn't get the necessary magic right.)
2009-10-24git-nofity: Try to shorten Gitweb URLsHolger Weiss1-1/+18
Instead of using the full SHA1 values of commit object names within Gitweb URLs, try to abbreviate them to a shorter unique name.
2009-10-24git-notify: Move the Gitweb URL to the bottomHolger Weiss1-1/+1
In commit notifications, specify the Gitweb URL (if any) at the bottom of the ASCII "table" which summarizes the commit. That looks better.
2009-10-24git-notify: Truncate summary after 50 charactersHolger Weiss1-1/+15
If the first line of a commit message is longer than 50 characters, truncate it before adding the resulting string to the subject line of a notification. This makes sure the subject line won't get too long (unless the commit author name is unusually long, which we don't check). The Git User's Manual recommends keeping the first line of a commit message shorter than that, anyway: | Though not required, it's a good idea to begin the commit message with | a single short (less than 50 character) line summarizing the change, | followed by a blank line and then a more thorough description. Tools | that turn commits into email, for example, use the first line on the | Subject line and the rest of the commit in the body. [ http://www.kernel.org/pub/software/scm/git/docs/user-manual.html ]