Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341069 - Configuring a push ref specification for 'tags/myTag' proposes 'tags/myTag' as destination ref which results in push to 'refs/tags/tags/myTag'
Summary: Configuring a push ref specification for 'tags/myTag' proposes 'tags/myTag' a...
Status: RESOLVED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 0.12   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-28 04:43 EDT by Edwin Kempin CLA
Modified: 2011-08-31 08:14 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Edwin Kempin CLA 2011-03-28 04:43:01 EDT 
Steps to reproduce:
1. create a tag 'refs/tags/myTag'
2. open the push dialog and enter 'tags/myTag' as source ref
3. press tab to set focus onto the destination ref input field
4. the destination ref is automatically set to 'tags/myTag'
5. add this push ref specification ('tags/myTag:tags/myTag')
6. push and see that the push is done to 'refs/tags/tags/myTag'

What is expected?
It is expected that either the push would be done to 'refs/tags/myTag' or that the proposed value for the destination ref would be 'refs/tags/myTag' instead of 'tags/myTag'.

Having 'refs/tags/myTag:refs/tags/myTag' as push ref specification works as expected.
Comment 1 Stefan Lay CLA 2011-07-06 10:43:31 EDT 
Fix proposed at http://egit.eclipse.org/r/#change,3836
Comment 2 Matthias Sohn CLA 2011-08-31 08:14:45 EDT 
merged as f22b04d49b43b0d1c06f59d17352ef04875b7cd0