From: Junio C Hamano <junkio@cox.net>
To: Thomas Glanzmann <thomas@glanzmann.de>
Cc: GIT <git@vger.kernel.org>
Subject: Re: Publishing Question: First time Pushing to nonexsiting directory
Date: Mon, 19 Feb 2007 00:33:22 -0800 [thread overview]
Message-ID: <7vk5yea6nh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070219073526.GA26531@cip.informatik.uni-erlangen.de> (Thomas Glanzmann's message of "Mon, 19 Feb 2007 08:35:26 +0100")
Thomas Glanzmann <thomas@glanzmann.de> writes:
> I thought that there is a command available which I can use to push a
> repository to a remote nonexisting location (that gets created on the
> fly) ...
Sorry, there isn't.
> I thought that I read a comment from Linus(?) long time ago to how to obtain
> that. But I am unable to find the e-mail in my archives. If there is no
> standard way, how do you do it? Just rsync the files and change the
> 'origin'?
What you remember might be this one:
http://thread.gmane.org/gmane.comp.version-control.git/31351/focus=31610
Even if it isn't, it is worth a read. Look for "The creation of
a new archive tends to" and "really _has_ to be separate".
There was another discussion around this topic as well:
http://thread.gmane.org/gmane.comp.version-control.git/32040/focus=32108
which I think is a possible design in the right direction, but I
did not hear much from the users (as you can see in the archive
link above) so it hasn't materialized. The only real improvement
that came out of the thread is deletion of a branch at the remote
site with "git-push :refs/heads/to-be-removed".
Another ancient one is:
http://thread.gmane.org/gmane.comp.version-control.git/12651/focus=12667
prev parent reply other threads:[~2007-02-19 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 7:35 Publishing Question: First time Pushing to nonexsiting directory Thomas Glanzmann
2007-02-19 8:10 ` Shawn O. Pearce
2007-02-19 19:44 ` Thomas Glanzmann
2007-02-19 20:03 ` Shawn O. Pearce
2007-02-19 20:10 ` Thomas Glanzmann
2007-02-19 8:33 ` Junio C Hamano [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=7vk5yea6nh.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=thomas@glanzmann.de \
/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