On 05.09.2008, at 18:42, Tchalvak wrote:
> > Saying " just don't push to a dirty index" is disappointing because it > kinda goes completely against the whole point of having a - > distributed- RCS. When pushing to another repo that has a working copy, the working copy and the index don't get touched. So the index isn't involved anyway. > For example, if I want to transfer changes in files between machine A > and machine B, both necessarily need to have a working copy. That > means that I definately need 2 locations with git initialized already > repo A and repo B. Saying that I should then create a repo C, and > push and pull all changes to repo C is like saying: Create a > centralized repository. Which part of the point of being a > distributed RCS is you shouldn't need to rely on a centralized > repository. That's what hooks are for. You can automatically update the working copy (or whatever else you want to do). See .git/hooks/post-receive for more info. regards, Markus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
