Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-10-06 Thread David McLaughlin
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26004/#review55564 --- Ship it! Ship It! - David McLaughlin On Oct. 6, 2014, 7:30 p.m.,

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-10-06 Thread Mark Chu-Carroll
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26004/ --- (Updated Oct. 6, 2014, 3:30 p.m.) Review request for Aurora, David McLaughlin a

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-10-06 Thread David McLaughlin
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26004/#review2 --- src/test/python/apache/aurora/client/cli/test_supdate.py

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-10-06 Thread Mark Chu-Carroll
> On Sept. 24, 2014, 6:28 p.m., David McLaughlin wrote: > > What was the rationale for hiding update IDs from the user and making job > > key the parameter for update status? It's nice you can quickly see if a job > > key has an update in progress.. but what happens if you're wanting to see a

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-10-06 Thread Mark Chu-Carroll
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26004/ --- (Updated Oct. 6, 2014, 9:16 a.m.) Review request for Aurora, David McLaughlin a

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-10-02 Thread Mark Chu-Carroll
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26004/ --- (Updated Oct. 2, 2014, 4:41 p.m.) Review request for Aurora, David McLaughlin a

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-10-01 Thread David McLaughlin
> On Sept. 24, 2014, 10:28 p.m., David McLaughlin wrote: > > What was the rationale for hiding update IDs from the user and making job > > key the parameter for update status? It's nice you can quickly see if a job > > key has an update in progress.. but what happens if you're wanting to see a

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-10-01 Thread Mark Chu-Carroll
> On Sept. 24, 2014, 6:28 p.m., David McLaughlin wrote: > > What was the rationale for hiding update IDs from the user and making job > > key the parameter for update status? It's nice you can quickly see if a job > > key has an update in progress.. but what happens if you're wanting to see a

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-09-29 Thread Mark Chu-Carroll
> On Sept. 24, 2014, 6:28 p.m., David McLaughlin wrote: > > What was the rationale for hiding update IDs from the user and making job > > key the parameter for update status? It's nice you can quickly see if a job > > key has an update in progress.. but what happens if you're wanting to see a

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-09-24 Thread David McLaughlin
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26004/#review54466 --- What was the rationale for hiding update IDs from the user and makin

Re: Review Request 26004: Add "aurora update list" and "aurora update status" commands.

2014-09-24 Thread Zameer Manji
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26004/#review54457 --- Ship it! Ship It! - Zameer Manji On Sept. 24, 2014, 1:24 p.m., M