From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: lost again on syntax change - local repository?
Date: 28 Nov 2005 05:04:40 -0800 [thread overview]
Message-ID: <86hd9w7wk7.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <7v7jat2w6u.fsf@assigned-by-dhcp.cox.net>
>>>>> "Junio" == Junio C Hamano <junkio@cox.net> writes:
Junio> If it is not absolutely necessary that you need to use Cogito,
Junio> IOW, if git barebone Porcelains are good enough for your use,
Junio> the following may be adequate.
Well, then, you should get rid of cogito/Documentation/introduction.html,
if you don't plan on supporting the interfaces described there.
I'm really just starting out. I see that tutorial, and I want to do it.
Junio> $ echo >.git/remotes/origin <<EOF
Junio> URL: /path/to/remote.git/
Junio> Push: master
Junio> Pull: master:origin
Junio> EOF
Ugh, ugh ugh ugh.
Junio> $ git push origin
Junio> I said "may be" because I do not understand the sequence before
Junio> "At this point"; how your local.git is initially set up to
Junio> relate to the remoge.git. I do not see local.git being created
Junio> by cloning remote.git.
I can't, because I have to do the first push. This is what I was told
last time!
I'm doing what I'm told, and now more things are breaking. This is
frustrating.
I'm not saying that you guys aren't doing a hell of a job. I'm just
coming at this from a user's perspective, and trying to describe it to
others. I'm not comfortable yet, because every time I try to do what
the manuals say, it breaks. Perhaps y'all are secretly working around
every broken thing, but I don't know enough to do that.
Junio> But modulo that the above should work
Junio> fine; I do that as a cheap backup on my local machine.
So, give me the exact steps, using "cg" to:
create a "remote" repo on my disk
create a "local" repo on my disk
set up the linkage between remote and local
push from local to remote
pull from remote to local
And if it ever needs a command like "cat" or "echo", something is
wrong. I'll accept a "git-" command for one or two of the steps, but
that feels like dropping into assembler instead of C.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-11-28 13:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 2:01 lost again on syntax change - local repository? Randal L. Schwartz
2005-11-28 5:11 ` Junio C Hamano
2005-11-28 6:36 ` Alecs King
2005-11-28 13:04 ` Randal L. Schwartz [this message]
2005-11-28 10:48 ` Petr Baudis
2005-11-28 13:09 ` Randal L. Schwartz
2005-11-28 13:41 ` Petr Baudis
2005-11-28 13:45 ` Randal L. Schwartz
2005-11-28 13:59 ` Randal L. Schwartz
2005-11-28 14:34 ` Petr Baudis
2005-11-28 14:46 ` Randal L. Schwartz
2005-11-28 19:15 ` Petr Baudis
2005-11-28 19:25 ` Randal L. Schwartz
2005-11-28 20:53 ` Petr Baudis
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=86hd9w7wk7.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--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;
as well as URLs for NNTP newsgroup(s).