summaryrefslogtreecommitdiffstats
path: root/tools/git-notify
AgeCommit message (Collapse)AuthorFilesLines
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-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-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 ]
2009-10-24git-notify: Send notifications on ref changes, tooHolger Weiss1-22/+68
Do not only generate notifications on commits, but also if a branch head or lightweight tag was created, removed, or modified. Notifications on branch head updates are omitted if one or more commit notification have been generated and the branch head now references a descendant of the originally referenced commit (which should be the usual case).
2009-10-24git-notify: Call git-rev-list(1) via a subroutineHolger Weiss1-9/+26
Add a subroutine which abstracts away executing git-rev-list(1) and checking the result in order to avoid code duplication.
2009-10-24git-notify: Mention the committer where applicableHolger Weiss1-0/+1
If the committer is not the author of the commit, mention the committer in addition to the author.
2009-10-24git-notify: New subroutine for column alignmentHolger Weiss1-5/+32
Most notifications include an ASCII "table" with two columns. The formatting of these columns is now handled by the new format_table() subroutine, so that the alignment can easily be changed in the future.
2009-10-24git-notify: Ignore "empty" commitsHolger Weiss1-4/+6
Omit notifications regarding commits which don't change the tree whatsoever.
2009-10-24git-notify: Remove unused tag notification codeHolger Weiss1-55/+22
The code which handles notifications regarding tags was unused, as only objects listed by git-rev-list(1) are considered, and git-rev-list(1) never spits out the sha1 of a tag object.
2009-10-24git-notify: Save author without trailing spaceHolger Weiss1-1/+1
Adjust the regular expression which catches the commit author name so that it doesn't include the space character which follows that name.
2009-10-24Import git-update-mirror and git-notifyHolger Weiss1-0/+431
Import the (self-written) git-update-mirror script, which updates clones of Git repositories and then calls git-notify (in just the same way as a post-receive hook would be called by Git). The git-notify script is imported from git://source.winehq.org/git/tools.git (commit: 03d66f34) and generates notifications on repository changes. We'll use these scripts for generating our commit e-mails.