Git development
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-branch, older repos and more confusion
Date: Thu, 12 Apr 2007 02:22:00 -0400	[thread overview]
Message-ID: <20070412062200.GA31788@coredump.intra.peff.net> (raw)
In-Reply-To: <46a038f90704112316v4aaa6246s9e07a3af8262b119@mail.gmail.com> <46a038f90704112300k3abd66d0nc4372962dbee8616@mail.gmail.com>

On Thu, Apr 12, 2007 at 06:16:20PM +1200, Martin Langhoff wrote:

> And I think I got it sussed out with:
> 
>   git-clone <repo> mydir
>   cd mydir
>   git-push origin origin/v1.9-maint:refs/heads/v1.9-clientname
>   git-checkout --track -b v1.9-clientname origin/v1.9-clientname

OK, I had misunderstood what you wanted. Yes, that should work, though I
think you will need to do a 'git-fetch' between your push and checkout.

> And then git-pull / git-push will "do the right thing". And `git-pull
> origin/v1.9-maint` will trigger a fetch & merge.

Actually, it should be "git-pull origin v1.9-maint". Of course, you've
been fetching origin/v1.9-maint all along when you pull your other
branch, so you can do it without touching the network at all: "git-merge
origin/v1.9-maint".

-Peff

      parent reply	other threads:[~2007-04-12  6:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12  4:14 git-branch, older repos and more confusion Martin Langhoff
2007-04-12  4:23 ` Jeff King
2007-04-12  4:54   ` Sam Vilain
2007-04-12  5:06     ` Martin Langhoff
2007-04-12  5:05   ` Martin Langhoff
2007-04-12  5:21     ` Jeff King
2007-04-12  6:00       ` Martin Langhoff
2007-04-12  6:16         ` Martin Langhoff
2007-04-12  6:22         ` Jeff King [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=20070412062200.GA31788@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@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