Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369606 - need to be able to push a specific commit (not all)
Summary: need to be able to push a specific commit (not all)
Status: RESOLVED INVALID
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: 0.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 17:40 EST by Susan McCourt CLA
Modified: 2012-01-24 20:22 EST (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 Susan McCourt CLA 2012-01-24 17:40:13 EST 
I am reviewing code contributions today.
I reviewed the first commit, it looked reasonable, so I cherry picked it.  Then I tested it to make sure it did what I thought, and I was unsure.  Wrote a note in the bug to the contributor.

Found the next commit, cherry picked it, tested it, I like it.
How can I push just this commit from my master branch?
Comment 1 Susan McCourt CLA 2012-01-24 17:43:49 EST 
this is really a philosophical question about the contribution workflow, so I'll update bug 369591.  I think the answer to this particular question is that I should be making a branch for each contribution.  But the whole workflow is just so cumbersome that I was trying to cheat and cherry pick all the commits to master.
Comment 2 Susan McCourt CLA 2012-01-24 20:22:20 EST 
I updated the wiki page for processing contributions to remind the committer to make a branch first.   (yes we should know that but a reminder never hurts).