Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324365 - [sync] SHA1 should be at the end of changeset names
Summary: [sync] SHA1 should be at the end of changeset names
Status: RESOLVED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 0.9.0-M3   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-02 20:53 EDT by Benjamin Muskalla CLA
Modified: 2010-09-08 17:09 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 Benjamin Muskalla CLA 2010-09-02 20:53:59 EDT 
When synchronzing with change sets, having all these SHA1 values in front of the commit shortnames has no real value for the user. We should rather push them at the end of the name, maybe in a light gray color.
Comment 1 Benjamin Muskalla CLA 2010-09-02 21:41:57 EDT 
Code review at http://egit.eclipse.org/r/#change,1515
Comment 2 Dariusz Luksza CLA 2010-09-04 14:32:54 EDT 
This behavior is based on:
git log --oneline

and I would prefer to keep it as is now.
Comment 3 Benjamin Muskalla CLA 2010-09-04 21:43:45 EDT 
This also makes sense for the git cli. But in EGit, we mostly don't work with the sha1 values but rather with selections. Thus I think the sha1 values should not be too prominent in the ui.
Comment 4 Benjamin Muskalla CLA 2010-09-08 17:09:28 EDT 
This has been merged with d842c88527601fd4ff5cd8e9161a78ae05d58dd9.