git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Big Lebowski <duderino.lebowski@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Getting Commits from One Repository to Another
Date: Thu, 21 May 2009 00:04:51 -0400	[thread overview]
Message-ID: <20090521040451.GC8091@sigill.intra.peff.net> (raw)
In-Reply-To: <7D9240D0-C8BA-40C6-A89E-8BC7E08B1163@gmail.com>

On Wed, May 20, 2009 at 07:37:54PM -0400, Big Lebowski wrote:

> Essentially, when I came on a project, a git repository was made  
> available to me (lets call that 'public_repo'). That repository was put up 
> on an unfuddle account, as an initial check-in; it was not cloned from the 
> repository they were working on (lets call that 'private_repo'). I wrote 
> some code, and pushed it to the repository. Now that I guess they feel 
> comfortable with me, they reveal to me the private_repo.
>
> How do I get my code from public_repo to private_repo?

You could just repeat the push you made to public_repo to private_repo.
Or you could push to private_repo from public_repo, or pull from
public_repo to private_repo. One of the results of git's distributed
nature is that a commit is a commit is a commit. It doesn't matter where
it comes from: pushing or pulling the same commit (i.e., the same sha-1
commit id) will give the same results.

Does that make sense? If not, can you be more specific about the setup
(i.e., which commands were run to create public_repo and your personal
clone)? Without that, it's hard to offer more specific advice.

-Peff

  reply	other threads:[~2009-05-21  4:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 23:37 Getting Commits from One Repository to Another Big Lebowski
2009-05-21  4:04 ` Jeff King [this message]
2009-05-21  9:12   ` Matthieu Moy
2009-05-21 20:08     ` Ryan
2009-05-22  7:26       ` Jeff King

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=20090521040451.GC8091@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=duderino.lebowski@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).