git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mike Gant" <mwgant@gmail.com>
To: git@vger.kernel.org
Subject: Re: git clone operation
Date: Tue, 19 Aug 2008 20:27:18 -0600	[thread overview]
Message-ID: <8f282e3b0808191927t7c202a2dvdff678bcec60d87f@mail.gmail.com> (raw)
In-Reply-To: <8f282e3b0808191923w18001cc6sef828d94b35e40c6@mail.gmail.com>

> 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?

      reply	other threads:[~2008-08-20  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 18:44 git clone operation Mike Gant
2008-08-17 19:23 ` Jakub Narebski
2008-08-17 19:38   ` Björn Steinbrink
2008-08-20  2:23     ` Mike Gant
2008-08-20  2:27       ` Mike Gant [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8f282e3b0808191927t7c202a2dvdff678bcec60d87f@mail.gmail.com \
    --to=mwgant@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).