torsdag 13 november 2008 21:27:42 skrev Farrukh Najmi: > A totally separate issue I have to sort out is how to handle multiple > unrelated transactions that are modifying the same git repo. If a > transaction needs to be rolled back how do roll back exactly some > changes in some files in git that were impacted by the transaction. This > is not easy because git (and most VCS) do not have transaction isolation > like databases do. Any suggestions? Updating the head ref is the hard part, but we have locking already there and it is atomic on any sane file system. There is no waiting implemented so one gets an error if two threads try to update the same head simultaneously. Seems doable I'd say. For server use one could wrap the repo with a real database, and just let the disk based refs mirror the database view, though that is quite a bit off focus for my own needs. > I am not very well versed in tag libraries myself. My situation is one > where everything happens inside a SOAP service endpoint and so I suspect > JSP tag libraries are not likely to be useful in that situation. Let me > know if I am wrong in this assessment. not at all. -- robin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
