Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350012 - [user] The user should be asked to provide Git name/mail before first init/clone
Summary: [user] The user should be asked to provide Git name/mail before first init/clone
Status: RESOLVED WONTFIX
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P4 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 349868
Blocks:
  Show dependency tree
 
Reported: 2011-06-22 04:01 EDT by Szymon Brandys CLA
Modified: 2015-05-05 16:21 EDT (History)
2 users (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 Szymon Brandys CLA 2011-06-22 04:01:48 EDT 
We need to ask to set the mail and name in the user profile, before first clone or init. Otherwise commits will be done with empty or some default name and mail.
Comment 1 Szymon Brandys CLA 2012-02-14 08:11:56 EST 
Git Init and Clone takes the user name/mail from the user profile and create new repos with these settings. Could these Git operations report an error when the user profile does not contain these two settings instead of falling back to some env value?
Comment 2 Tomasz Zarna CLA 2012-02-14 09:02:18 EST 
User name and mail are not needed when cloning a repo, they shouldn't be required. Same should be true for initing a repo, it's not in Orion case due to a workaround introduced for bug 339610 in JGit, see bug 339609 comment 1. We should get rid of the workaround, make sure we are able to handle repos with no HEAD and disallow committing when no name/mail is available (which afaik already takes place).

I will have a loot at it during 0.5. It's a low priority though.
Comment 3 John Arthorne CLA 2015-05-05 16:21:11 EDT 
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:


https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html