Forking is essentially a server-side clone, that's all. The whole point is to give you access to a repo you can push to since it's highly unlikely you have write access to the repo you're forking from.
On Wed, Mar 3, 2010 at 4:14 PM, cc <[email protected]> wrote: > Is there anything else that happens that I should know about? > I'm looking at how I might setup a similar workflow when I'm forced to > stay behind a customer's firewall, for example. > > On Mar 3, 4:45 pm, Tekkub <[email protected]> wrote: > > "Basically" yes > > > > On Mar 3, 2010 3:34 PM, "cc" <[email protected]> wrote: > > > > Is it basically equivalent to a "git clone --mirror URL" ? > > > > -- > 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]<github%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/github?hl=en. > > -- 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.
