From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb@sourceware.org
Subject: Re: gdb-python git repository
Date: Fri, 20 Jun 2008 14:10:00 -0000 [thread overview]
Message-ID: <20080620101014.s394xuwzb40owkk0@imap.linux.ibm.com> (raw)
In-Reply-To: <jewskktr6q.fsf@sykes.suse.de>
Zitat von Andreas Schwab <schwab@suse.de>:
>> That line was there because the latest git version at the time had a bug
>> which would leave the origin blank when cloning a "HEADless" repository.
>
> Would it be possible to add a HEAD to the repository?
I don't know.
>> It was fixed since then, so if you use a recent git then it is unnecessary.
>
> At least it would have to use the correct url.
It was correct for people who have commit access and want to help with
development, which is the main purpose of that repository.
Of course, people are welcome to just follow what's going on there, but it
was not the primary intent of the instructions (we are posting patches to
the mailing list for that).
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2008-06-20 14:10 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
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 [this message]
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=20080620101014.s394xuwzb40owkk0@imap.linux.ibm.com \
--to=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
--cc=schwab@suse.de \
/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