Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339234 - [client] Making a commit with an empty message should not be allowed
Summary: [client] Making a commit with an empty message should not be allowed
Status: CLOSED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.2   Edit
Assignee: libing wang CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 10:39 EST by Tomasz Zarna CLA
Modified: 2011-09-01 11:42 EDT (History)
0 users

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 Tomasz Zarna CLA 2011-03-08 10:39:25 EST 
Neither EGit nor msysgit allow to make a commit with an empty message. We should prevent it as well. the REST API will return 400 for a request without a message, but apparently it's fine {"Message":""}. I will fix that on the server side, Libing will make a required change in the git-status page.
Comment 1 Tomasz Zarna CLA 2011-03-09 09:58:38 EST 
Server side fix in place -- f17e224...
Comment 2 libing wang CLA 2011-03-09 12:32:46 EST 
fixed at commit 49b42eaef426eb16b6e29888a03553940287fd72
.