git/list[1] front-page[2] threads[3] people[4] search[5] about
 

proper way to make cg-fetch work from originally git-clone'd tree

From
Randal L. Schwartz <merlyn@stonehenge.com>
Date
Nov 10, 2005, 13:51 UTC
Message-ID
<86mzkc4nlu.fsf@blue.stonehenge.com>

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!
Next: Petr Baudis
Message 1 of 3 in “proper way to make cg-fetch work from originally git-clone'd tree”
  1. Randal L. SchwartzNov 10, 2005
  2. Petr BaudisNov 11, 2005
  3. Randal L. SchwartzNov 11, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.