From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Starting a new project remotely
Date: Sun, 15 Jan 2006 15:01:58 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601151437240.25300@iabervon.org> (raw)
In-Reply-To: <7vd5it47lr.fsf@assigned-by-dhcp.cox.net>
On Sun, 15 Jan 2006, Junio C Hamano wrote:
> 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.
My general pattern is that I have an "origin" repository, which is public
and central. I do work in various other repositories, and push the results
to origin when I finish them. I create these with "git clone", so the
central point is called "origin" in each clone.
The odd case is when I start out; I have a repository with the initial
commit, and "origin" is blank. The desired result is that the central
location gets this commit, and the repository I'm starting from becomes
identical to any clone of the central location.
I don't create the initial commit in the central location because there's
no working tree there, and it's a pain to prepare a commit without one. I
suppose the alternative is to support cloning a blank repository, so I
could prepare the initial commit just like any later one.
Incidentally, I think it would be useful to have a script that creates a
remotes/ file given a command line like push or pull. Then you could use
"git pull" with a long command line until you were happy with the
behavior, and then make a shortcut out of it. It'd also be nice to have
the command list the remotes for you as well. If anyone's in the mood for
scripting and wants something to work on...
-Daniel
*This .sig left intentionally blank*
prev parent reply other threads:[~2006-01-15 20:00 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
2006-01-15 20:01 ` Daniel Barkalow [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=Pine.LNX.4.64.0601151437240.25300@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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