added write method to index #51

Merged
tobscher merged 1 commits from master into master 2014-02-23 08:49:31 -06:00
tobscher commented 2014-01-23 19:16:55 -06:00 (Migrated from github.com)

According to the following issue: https://github.com/libgit2/rugged/issues/254 you have to write out your index or you end up with a "weird" commit status when manually creating a commit object.

Is that the right approach after manually crafting a commit?

Tobscher

According to the following issue: https://github.com/libgit2/rugged/issues/254 you have to write out your index or you end up with a "weird" commit status when manually creating a commit object. Is that the right approach after manually crafting a commit? Tobscher
carlosmn commented 2014-01-25 01:40:10 -06:00 (Migrated from github.com)

More or less. You should write out the index before creating the commit, or it will be confusing if an error happens.

More or less. You should write out the index before creating the commit, or it will be confusing if an error happens.
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jcarr/git2go#51
No description provided.