repository

I have four branches like master -> origin/regacy, FeatureA -> origin/FeatureA. As you can see, I typed the wrong name. So I want to rename a remote branch name (origin/regacy → origin/legacy or origin/master) I try the command below: git remote rename regacy legacy But Git console returned an error message to me. error : Could not rename config section 'remote.regacy' to 'remote.legacy' How can I solve this problem? CodeWizard You can't directly rename a remote branch. You have to delete it and then re-push it. Renaming a branch # Rename the local branch to the new name git branch -m <old

I'm trying to brush up on my design pattern skills, and I'm curious what are the differences between these patterns? All of them seem like they are the same thing - encapsulate the database logic for a specific entity so the calling code has no knowledge of the underlying persistence layer. From my brief research all of them typically implement your standard CRUD methods and abstract away the database-specific details. Apart from naming conventions (e.g. CustomerMapper vs. CustomerDAO vs. CustomerGateway vs. CustomerRepository), what is the difference, if any? If there is a difference, when

I have to admit I have been carrying the "Repository should not return IQueryable" banner because it is harder to test. I have been influenced by the answers to other questions like this and this . This morning I've been reading ScuttGu's blog about ASP.NET vNext where he details Model Binding using a SelectMethod that seems to rely on IQueryable for paging and sorting. Do you think this will force us to reconsider the role IQueryable plays in repositories? DDD Repository should encapsulate data access technicalities: Definition: A Repository is a mechanism for encapsulating storage, retrieval

I have a 1..* relationship between Review and Recommendations . The relevant portion of my model (which is also the POCO mapped by EF4): public class Review { public ICollection<Recommendations> Recommendations { get; set; } } On an Edit View , i represent the Recommendations as a set of checkboxes. When i try and add a new Recommendation as part of editing the Review (e.g check another box), nothing is happening - and i know why... I use the "stub technique" to update my entities - e.g i create a entity with the same key, attach it to the graph, then do ApplyCurrentValues . But this only

I read the subversion book and it is clear to me that subversion does not store individual files but only deltas in order to minimize disk space. Subversion also does the same with binary files as well (this used to be a huge weakness of CVS). However I do not understand the exact mechanism. When I commit a file what happens? Subversion stores only the diff (and already has the old version) Subversion deletes the previous version, stores the new file intact and creates a reverse diff in order to "re-create" the old version if needed. Something else that I haven't thought of. The first case