threads / discuss / 2430

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

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

## tl;dr

3 messages between Nov 10, 2005 and Nov 11, 2005.

replies: 2people: 2as markdown or json

Randal L. Schwartz· Nov 10, 2005, 13:51 UTC · lore

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!

Petr Baudis· Nov 11, 2005, 00:11 UTC · re: Randal L. Schwartz · lore

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

Dear diary, on Thu, Nov 10, 2005 at 02:51:57PM CET, I got a letter where "Randal L. Schwartz" <merlyn@stonehenge.com> said that...

Show 10 quoted lines

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

You should do what you did - it was just a warning. git-clone seems to have created only a 'remotes' entry, which Cogito doesn't understand (yet).

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

Any reason why you were unable to tell the main make 'doc install-doc'?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.

Randal L. Schwartz· Nov 11, 2005, 00:13 UTC · re: Petr Baudis · lore

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

>>>>> "Petr" == Petr Baudis <pasky@suse.cz> writes:

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

Petr> Any reason why you were unable to tell the main make 'doc install-doc'?

Because I didn't see it? :-)

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