path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* Move to a more recent django project structureJeremy Kerr2015-05-272-2/+2
| | | | | | | | | | This change updates patchwor to the newer project struture: we've moved the actual application out of the apps/ directory, and the patchwork-specific templates to under the patchwork application. This gives us the script in the top-level now. Signed-off-by: Jeremy Kerr <>
* post-receive: exclude commits from the patch update stepBrian Norris2014-07-241-1/+8
| | | | | | | | | | | | | | | | | | When merging upstream work related to other projects into your own project repository, you probably don't want to check for (and try to update) the status on every change-set in the merge. So add a list of references (branches, tags, commits, etc.) whose commits should be ignored in the patch update step. This could be used, for example, to set: EXCLUDE="refs/heads/upstream" Then when you're ready to merge in new upstream code, you first update the 'upstream' branch before pushing your own. Signed-off-by: Brian Norris <> Signed-off-by: Jeremy Kerr <>
* post-receive: Fix error message when pushing to an unmapped branchCarl Worth2014-01-291-1/+1
| | | | | | | | | | | | | | | | Previously, if STATE_MAP contained only refs/heads/master and a user pushed to a branch such as refs/heads/stable, the hook emitted a misleading error message: E: no mapping for refname refs/heads/master Fix this by correctly printing the reference being looked for, rather than the reference most recently found in STATE_MAP. Also, reword the message slightly to point the user to STATE_MAP and to use an actual word "branch" instead of the non-word "refname". Signed-off-by: Carl Worth <> Signed-off-by: Jeremy Kerr <>
* Make the post-receive hook more efficient (using pwclient info, not view)Carl Worth2014-01-291-2/+2
| | | | | | | | | | | | | | Older versions of patchwork shipped with a version of pwclient that had the view command, but not info command. Now that info exists, it's inefficient to use it to obtain the patchwork ID value, (since it requires the server to send the entire patch content in response to an XML RPC request). So be kind to the server by using info instead, (which has a small, fixed-length response). Signed-off-by: Carl Worth <> Signed-off-by: Jeremy Kerr <>
* tools/post-receive.hook: don't update the previously pushed commitCarl Worth2014-01-291-1/+1
| | | | | | | | | | Previously, the post-receive hook would always examine one commit that had been previously pushed, (when the purpose of the hook is only to example newly-pushed commits). We fix this by simply dropping the '^' in the commit-range specification. Signed-off-by: Carl Worth <> Signed-off-by: Jeremy Kerr <>
* patchwork-update-commits: add missing `update` to command linePaul Menzel2011-03-301-1/+1
| | | | | | | | | Otherwise the following error is shown: Too many arguments specified Signed-off-by: Paul Menzel <> Signed-off-by: Jeremy Kerr <>
* patchwork-update-commits: autodetect patchwork install directorySascha Silbe2011-02-281-1/+2
| | | | | | | | Make patchwork-update-commits work from outside the Patchwork git repository so it can be used for other projects. Signed-off-by: Sascha Silbe <> Signed-off-by: Jeremy Kerr <>
* tools: add simple patchwork-update-commits scriptJeremy Kerr2010-08-101-0/+16
| | | | Signed-off-by: Jeremy Kerr <>
* tools: Update license for post-receive hook.Jeremy Kerr2010-08-101-2/+1
| | | | | | | Martin has allowed distribution under the GPL. Signed-off-by: Jeremy Kerr <>
* tools: Add a simple sample Git post-receive hookMartin Krafft2010-08-101-0/+73
This patch adds a post-receive hook to lib/git, which can be used to update Patchwork following a push to the Git repository. Surely, it can be improved. One thing to do would be to export the state map to git-config somehow. Signed-off-by: martin f. krafft <> Signed-off-by: Jeremy Kerr <>