From: Graeme Geldenhuys <graemeg@gmail.com>
To: git@vger.kernel.org
Subject: Re: Pushing to GitHub doesn't push all branches
Date: Mon, 13 Jul 2009 10:12:17 +0200 [thread overview]
Message-ID: <h3eqap$cov$1@ger.gmane.org> (raw)
In-Reply-To: <4A57639D.4020305@drmicha.warpmail.net>
Michael J Gruber wrote:
>
> Please don't! That's what we're here for ;)
:) Thanks.
> git for-each-ref --shell --format="git push -f origin :%(refname)"
> refs/remotes/|while read line; do eval $line;done
OK, done this. 'git ls-remote github' doesn't show any remotes/*
references anymore.
Oh by the way, I followed your advice and renamed 'origin' to 'github'
so it makes a bit more sense. I used the following command:
$ git remote rename origin github
>
> git config remote.origin.push '+refs/remotes/*:refs/heads/*'
OK, I've done this, but I'm not 100% sure what this means. This is what
I think (from reading various git help and users guide). Any branches I
have which track remote references (from svn repository) will be pushed
to github as various head references (normal branches). Is this correct?
On our server, which contain the svn cloned repository and the one that
is only used for syncing svn -> our server -> github, I had to add a new
commit which represents the svn-ignore meta data to a .gitignore file. I
noticed I had to manually to a 'git checkout master' & 'git merge
remotes/trunk' to pull in new updates. I thin pushed that to github.
So what is my twice hourly cron script supposed to look like? Is the
following still ok?
========[ script executed by cron every 30 minutes ]============
#!/bin/sh
GIT="/usr/local/bin/git"
# FPC repository
cd /mnt/samba/git/fpc.git/
$GIT checkout master
$GIT svn fetch
$GIT gc --auto
$GIT push github master
==============================
Or do I need to add a new line after '$GIT svn fetch' that does a merge.
==============================
$GIT svn fetch
$GIT merge remotes/trunk
...
push to github
==============================
Also what do I do with the other branch I want to track. It's called
remotes/fixes_2_2.
I believe I need to first create a local branch.
git branch --track fixes_2_2 remotes/fixes_2_2
What do I need to modify in my cron script to keep both the master &
fixes_2_2 branches in sync with SubVersion and push both to GitHub. I
want Github to show two branches: master & fixes_2_2
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
next prev parent reply other threads:[~2009-07-13 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 13:24 Pushing to GitHub doesn't push all branches Graeme Geldenhuys
2009-07-10 14:45 ` Michael J Gruber
2009-07-10 14:58 ` Michael J Gruber
2009-07-10 15:07 ` Graeme Geldenhuys
2009-07-10 15:51 ` Michael J Gruber
2009-07-13 8:12 ` Graeme Geldenhuys [this message]
2009-07-13 11:01 ` Michael J Gruber
2009-07-13 13:41 ` Graeme Geldenhuys
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='h3eqap$cov$1@ger.gmane.org' \
--to=graemeg@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).