> On Jan. 20, 2016, 2:30 a.m., Colin Ma wrote: > > dev-support/upload-patch.py, line 168 > > <https://reviews.apache.org/r/42495/diff/1/?file=1201503#file1201503line168> > > > > The patch name is the same, add some suffix will be easy to find the > > lastest one. > > For example, in SQOOP-2792, all patches have the same name and the > > update time is yesterday, I don't know which one should be used. > > Jarek Cecho wrote: > This is actually something that JIRA itself is solving for us - all > "older" files have greyed out name whereas only the "most up to date" variant > is blue (and that is the one that should be used). > > I've heard this concern a few times already though, so I guess that > people are not aware of this "feature". Perhaps we should improve it to make > it easier for everyone. Would you mind doing that as part of separate JIRA > though?
don't we already get this kind of thing through the review board revision history? - Abraham ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/42495/#review115320 ----------------------------------------------------------- On Jan. 19, 2016, 11:13 a.m., Jarek Cecho wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/42495/ > ----------------------------------------------------------- > > (Updated Jan. 19, 2016, 11:13 a.m.) > > > Review request for Sqoop and Jarek Cecho. > > > Bugs: SQOOP-2796 > https://issues.apache.org/jira/browse/SQOOP-2796 > > > Repository: sqoop-sqoop2 > > > Description > ------- > > Our process to submit a contribution to Sqoop has quite a few steps: > > # Clone repo > # Work on the fix/feature/... > # Generate text patch > # Upload it to review board > # Don't forget to publish the review board > # Upload the patch to JIRA > # Switch the JIRA to "Patch available" > > Forgetting to do any of those steps will lead to a quite unnecessary delays > with accepting the patch so I would like to automate steps 3-7 with simple > script that one can call from the computer and all that will happen > "magically" automatically. > > > Diffs > ----- > > dev-support/upload-patch.py PRE-CREATION > > Diff: https://reviews.apache.org/r/42495/diff/ > > > Testing > ------- > > > Thanks, > > Jarek Cecho > >
