Ivan Gorbachev created HIVE-3498:
------------------------------------
Summary: hivetest.py fails with --revision option
Key: HIVE-3498
URL: https://issues.apache.org/jira/browse/HIVE-3498
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Reporter: Ivan Gorbachev
Assignee: Ivan Gorbachev
How to reproduce outside hivetest.py:
1. Clone git://git.apache.org/hive.git
2. Run ant arc-setup
3. Run arc patch <rev>
Output:
{quote}
This diff is against commit
https://svn.apache.org/repos/asf/hive/trunk@1382631, but the commit is
nowhere in the working copy. Try to apply it against the current working
copy state? (d5f66df1edfff2645f225298e225dbccc70d97ff) [Y/n]
{quote}
If you choose 'Y' it suggests you to complete 'merge-message' and then prints:
{quote}
Select a Default Commit Range
You're running a command which operates on a range of revisions (usually,
from some revision to HEAD) but have not specified the revision that should
determine the start of the range.
Previously, arc assumed you meant 'HEAD^' when you did not specify a start
revision, but this behavior does not make much sense in most workflows
outside of Facebook's historic git-svn workflow.
arc no longer assumes 'HEAD^'. You must specify a relative commit explicitly
when you invoke a command (e.g., `arc diff HEAD^`, not just `arc diff`) or
select a default for this working copy.
In most cases, the best default is 'origin/master'. You can also select
'HEAD^' to preserve the old behavior, or some other remote or branch. But you
almost certainly want to select 'origin/master'.
(Technically: the merge-base of the selected revision and HEAD is used to
determine the start of the commit range.)
What default do you want to use? [origin/master]
{quote}
There isn't the same behavior for svn checkout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
