From: Nick Roberts <nickrob@snap.net.nz>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: gdb-python git repository
Date: Thu, 19 Jun 2008 06:07:00 -0000 [thread overview]
Message-ID: <18521.63323.996811.228266@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080619010648.r379fi19ck88g484@imap.linux.ibm.com>
> I believe git:// uses ssh underneath, so by switching to http you shouldn't
> be getting any passphrase prompts I guess... (wave hand)
I had presumed it was just a more efficient protocol for downloading the
repository. At the end I got:
...
cat: /home/nickrob/mainline/.git/refs/remotes/origin/master: No such file or directory
fatal: : not a valid SHA1
fatal: Not a valid object name HEAD
but it seemed to work, as I could build GDB and git-pull now gives:
...
Fetching refs/heads/python-revisited from http://git.gitorious.org/gdb-python/mainline.git using http
Already up-to-date.
I guess CVS has a similar set of arcane rules, but at least they're ones that I
generally know.
Perhaps it's worth putting how to do this `anonymous' clone on the Wiki.
Thanks.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-06-19 6:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 22:34 Nick Roberts
2008-06-18 23:17 ` Thiago Jung Bauermann
2008-06-18 23:31 ` Nick Roberts
2008-06-19 5:07 ` Thiago Jung Bauermann
2008-06-19 6:07 ` Nick Roberts [this message]
2008-06-19 8:20 ` Andreas Schwab
2008-06-19 8:27 ` Nick Roberts
2008-06-19 8:30 ` Andreas Schwab
2008-06-20 2:20 ` Nick Roberts
2008-06-20 9:01 ` Andreas Schwab
2008-06-20 9:27 ` Nick Roberts
2008-06-20 9:41 ` Andreas Schwab
2008-06-20 10:13 ` Nick Roberts
2008-06-19 8:28 ` Andreas Schwab
2008-06-20 7:15 ` Thiago Jung Bauermann
2008-06-20 9:02 ` Andreas Schwab
2008-06-20 14:10 ` Thiago Jung Bauermann
2008-06-21 7:32 ` Andreas Schwab
2008-06-21 15:54 ` Thiago Jung Bauermann
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=18521.63323.996811.228266@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bauerman@br.ibm.com \
--cc=gdb@sourceware.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