From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Starting a new project remotely
Date: Sun, 15 Jan 2006 11:24:48 -0800 [thread overview]
Message-ID: <7vd5it47lr.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0601151323320.25300@iabervon.org> (Daniel Barkalow's message of "Sun, 15 Jan 2006 13:45:01 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> Is there something currently that acts like git-clone, except that it sets
> up automatic connections in the opposite direction? That is, you run it in
> a repository with no origin, and it pushes the data to the specified
> location (which probably needs to be set up already as an empty
> repository) and sets the local side's origin remote to the location given.
The "git push" command allows you to push into an empty or even
unrelated destination, but I do think there no wrapper that
creates remotes/ file. BTW, calling that "origin" is probably
confusing. In the scenario you outlined, your local side is the
source and the remote is the sink.
FYI, here is what I have in my remotes/ko file to interact with
my kernel.org repository (the one that is mirrored out to the
public machines):
URL: zzz.kernel.org:/pub/scm/git/git.git/
Push: master
Push: +pu
Push: maint
Pull: master:refs/tags/ko-master
Pull: +pu:refs/tags/ko-pu
Pull: maint:refs/tags/ko-maint
and with this, I first run
$ git fetch ko
$ git show-branch master ko-master
to make sure I am not rewinding what I have already pushed out
by mistake, and then
$ git push ko
$ git push --tags ko ;# if I added a new tag
next prev parent reply other threads:[~2006-01-15 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 18:45 Starting a new project remotely Daniel Barkalow
2006-01-15 19:24 ` Junio C Hamano [this message]
2006-01-15 20:01 ` Daniel Barkalow
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=7vd5it47lr.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--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