git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dennis E. Slice" <dslice@morphometrics.org>
To: Phil Hord <phil.hord@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Sharing nested subparts of large repository?
Date: Mon, 26 Mar 2012 16:43:14 -0400	[thread overview]
Message-ID: <4F70D4E2.2010206@morphometrics.org> (raw)
In-Reply-To: <CABURp0r-uY_HH1jw6P9KUvg-XNhYShVLnfcTMH78atdTV9K89w@mail.gmail.com>



On 3/26/12 12:07 AM, Phil Hord wrote:
> On Sun, Mar 25, 2012 at 12:38 PM, LordSmoke<dslice@morphometrics.org>  wrote:
<...snip...>
>>
>> Would someone point me in the right direction to achieve my goals?
>
> There's a blog post detailing a similar workflow here:
> http://www.braintreepayments.com/devblog/our-git-workflow

Yes. That is exactly where I was heading in thinking about things and 
learning more about branches. gitx or gitg really help clarify the 
relationships and allow one to think better about the organization. I 
had looked at all this early on, but was too new to be anything other 
than confused. I have enough experience now to appreciate at least some 
of it.

TIA

>
> Grr... I think they used to have a section on keeping some parts of
> the project "forever private", but I don't see that now.
>
> Phil
>
>

  reply	other threads:[~2012-03-26 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 16:38 Sharing nested subparts of large repository? LordSmoke
2012-03-26  4:07 ` Phil Hord
2012-03-26 20:43   ` Dennis E. Slice [this message]
2012-03-28  9:52 ` Neal Kreitzinger
2012-03-28 17:52 ` LordSmoke
2012-03-29 20:05   ` LordSmoke
2012-04-05  8:32   ` LordSmoke

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=4F70D4E2.2010206@morphometrics.org \
    --to=dslice@morphometrics.org \
    --cc=git@vger.kernel.org \
    --cc=phil.hord@gmail.com \
    /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).