git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: proper way to make cg-fetch work from originally git-clone'd tree
Date: 10 Nov 2005 05:51:57 -0800	[thread overview]
Message-ID: <86mzkc4nlu.fsf@blue.stonehenge.com> (raw)


I tried git-fetch this morning, and it said I didn't have an origin,
which makes sense because I made the tree with git-clone, not cg-clone.

However, when I tried

        cg-branch-add origin rsync://rsync.kernel.org/pub/scm/git/git.git

it complained that I already had an origin!  It seems to work after
that, but what should I have done instead?  Is there a way to make
both cg-fetch and git-fetch to default to the same things?

By the way, my "make only if something changed" works now, because
I've separated cg-fetch and cg-merge.  My merge step looks like:

  cg-merge 2>&1 | grep -v 'already fully merged' && make prefix=/opt/git all install && (cd Documentation && make prefix=/opt/git all install)

-- 
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!

             reply	other threads:[~2005-11-10 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 13:51 Randal L. Schwartz [this message]
2005-11-11  0:11 ` proper way to make cg-fetch work from originally git-clone'd tree Petr Baudis
2005-11-11  0:13   ` Randal L. Schwartz

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=86mzkc4nlu.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --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;
as well as URLs for NNTP newsgroup(s).