Re: git clone operation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Thanks for your responses. I appreciate you guys taking the time to answer.
>
> After thinking about this, I still don't understand when I clone a
> repo why I will
> get the equivalent of whatever branch is active at the time of cloning? What
> was the process that led to this design decision?
>
> So that also got me thinking about work flows with git. Because of the way clone
> works it seems that you wouldn't want someone to clone your every day "work"
> repository? So do developers generally have a separate repository that they push
> to and others can clone? This repository may have only a 'master' branch (but
> probably others I seem to recall Junio describing other branches in the main git
> repository). Is this a 'normal' work flow?
>
> Thanks,
> Mike Gant
>

Also, I meant to add if the above work flow is the git way of
development, is this
the purpose of a bare repository?
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux