From: Petr Baudis Date: Fri, 11 Nov 2005 00:11:48 GMT Subject: Re: proper way to make cg-fetch work from originally git-clone'd tree Message-ID: <20051111001148.GG30496@pasky.or.cz> In-Reply-To: <86mzkc4nlu.fsf@blue.stonehenge.com> Dear diary, on Thu, Nov 10, 2005 at 02:51:57PM CET, I got a letter where "Randal L. Schwartz" said that... > 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.