diff options
| author | Brian Norris <computersforpeace@gmail.com> | 2014-11-22 20:38:45 -0800 |
|---|---|---|
| committer | Jeremy Kerr <jk@ozlabs.org> | 2015-03-22 21:08:30 +0800 |
| commit | 7e072a3308fb43fba06e94e9b30d8c9f1638a77b (patch) | |
| tree | 4a17c1f8ae968853be70e13db8ebdd6a0419535c /apps | |
| parent | 1f3baf18e72b0b77c1987afceb4dbe9dca6676b4 (diff) | |
| download | patchwork-7e072a3308fb43fba06e94e9b30d8c9f1638a77b.tar.bz2 patchwork-7e072a3308fb43fba06e94e9b30d8c9f1638a77b.tar.xz | |
pwclient: add project option to single-patch commands
Previously, we could not target a particular server instance with the
apply, git-am, info, and view subcommands. Under a single-server design,
we never needed to target a particular project for a patch. We just
targeted the patch itself. But with the advent of multi-server
.pwclientrc configurations, we should allow pwclient to specify the
project for these commands.
This adds the '-p PROJECT' option to:
* apply
* git-am
* info
* view
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
Diffstat (limited to 'apps')
| -rwxr-xr-x | apps/patchwork/bin/pwclient | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/apps/patchwork/bin/pwclient b/apps/patchwork/bin/pwclient index 2a80981..483330e 100755 --- a/apps/patchwork/bin/pwclient +++ b/apps/patchwork/bin/pwclient @@ -359,6 +359,10 @@ def main(): 'id', metavar='ID', nargs='*', action='store', type=int, help='Patch ID', ) + hash_parser.add_argument( + '-p', metavar='PROJECT', + help='''Lookup patch in project''' + ) filter_parser = argparse.ArgumentParser(add_help=False, version=False) filter_parser.add_argument( |