git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Paul Dickson <paul@permanentmail.com>
Cc: git@vger.kernel.org
Subject: Re: Problems with cg-admin-setuprepo
Date: Tue, 13 Dec 2005 02:16:30 +0100	[thread overview]
Message-ID: <20051213011630.GB22159@pasky.or.cz> (raw)
In-Reply-To: <20051212180215.e9b687e4.paul@permanentmail.com>

Dear diary, on Tue, Dec 13, 2005 at 02:02:15AM CET, I got a letter
where Paul Dickson <paul@permanentmail.com> said that...
> On Mon, 12 Dec 2005 02:12:10 +0100, Petr Baudis wrote:
> >   this is Cogito version 0.16.1, the next stable release of the
> > human-friendly version control UI for the Linus' GIT tool.
> 
> The help from cg-admin-setuprepo say it will create the repo in the given
> directory, but doesn't say it must create the directory.
> 
>   $ mkdir ~/test
>   $ cg-admin-setuprepo ~/test
>   cg-admin-setuprepo: /home/dickson/test already exists

Good point. I've added it to the description.

> There seems to be a missing step in the help instructions:
> 
>   $ cg-admin-setuprepo ~/test/test1
>   $ cg-push
>   cg-push: where to push to?

You need to first add the remote branch to your local repository by the

	cg-branch-add origin ~/test/test1

command. I've added it to the instructions.

Thanks,

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

  reply	other threads:[~2005-12-13  1:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12  1:12 [ANNOUNCE] Cogito-0.16.1 Petr Baudis
2005-12-12  1:14 ` Petr Baudis
2005-12-12  3:03   ` Don Koch
2005-12-13  1:02 ` Problems with cg-admin-setuprepo Paul Dickson
2005-12-13  1:16   ` Petr Baudis [this message]
2005-12-13  1:26 ` [ANNOUNCE] Cogito-0.16.1 Paul Dickson
2005-12-13 16:56   ` Petr Baudis
2005-12-13 18:02     ` Paul Dickson
2005-12-13 22:31       ` Petr Baudis
2005-12-14  1:40         ` Paul Dickson

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=20051213011630.GB22159@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=paul@permanentmail.com \
    /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).