Bug 343638 – Put a better message when branch.master.merge entry is missing

Bug 343638 - Put a better message when branch.master.merge entry is missing


Summary:	Put a better message when branch.master.merge entry is missing

Status:	CLOSED DUPLICATE of bug 343593

Product:	EGit
Classification:	Technology
Component:	UI
Version:	0.11
Hardware:	All All

Importance:	P3 normal with 1 vote (vote)
Target Milestone:	---
Assigned To:	Project Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2011-04-22 04:11 EDT by Maxime Jeanmart
Modified:	2013-09-28 12:04 EDT (History)
CC List:	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 Maxime Jeanmart

2011-04-22 04:11:54 EDT

If the branch.master.merge entry is not specified in configuration, you get the following error message: "no values for key branch.master.merge" found in configuration". From that message, it's not easy to know what to do to solve the issue.
It's probably possible to improve usability by adding some explanations like "add the branch.master.merge entry in the repository config file" or something like that. With an example, it's even better. (just a suggestion, of course)

Comment 1 Gunnar Wagenknecht

2011-04-23 16:53:59 EDT

IMO, if there is just one remote branch in the repo EGit should be even smarter and assume that the user wanted to pull from this branch. That would improve usability even more.

Comment 2 Robin Stocker

2013-09-28 12:04:11 EDT

Even better, we should show a wizard which helps with setting up the "upstream", see bug 343593.

*** This bug has been marked as a duplicate of bug 343593 ***