From: Michael J Gruber <git@drmicha.warpmail.net>
To: unlisted-recipients:; (no To-header on input)
Cc: Graeme Geldenhuys <graemeg@gmail.com>, git@vger.kernel.org
Subject: Re: Pushing to GitHub doesn't push all branches
Date: Fri, 10 Jul 2009 16:58:25 +0200 [thread overview]
Message-ID: <4A575711.1050007@drmicha.warpmail.net> (raw)
In-Reply-To: <4A575416.2090304@drmicha.warpmail.net>
Michael J Gruber venit, vidit, dixit 10.07.2009 16:45:
...
> I think what you really want is to push everything under remote
> (assuming there are only svn branches) into proper heads on github, i.e.
> a refspec like '+refs/remotes/*:refs/*' for your pushes.
Uhm, make that '+refs/remotes/*:refs/heads/*' ;)
next prev parent reply other threads:[~2009-07-10 14:58 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 [this message]
2009-07-10 15:07 ` Graeme Geldenhuys
2009-07-10 15:51 ` Michael J Gruber
2009-07-13 8:12 ` Graeme Geldenhuys
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=4A575711.1050007@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=graemeg@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).