From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix typo in gdb/testsuite/gdb.arch/thumb2-it.S
Date: Mon, 21 Oct 2013 15:37:00 -0000 [thread overview]
Message-ID: <m3sivuab50.fsf@redhat.com> (raw)
In-Reply-To: <52654747.2030909@mentor.com> (Tom de Vries's message of "Mon, 21 Oct 2013 17:24:55 +0200")
On Monday, October 21 2013, Tom de Vries wrote:
> On 21/10/13 16:51, Pedro Alves wrote:
>> On 10/20/2013 02:55 PM, Tom de Vries wrote:
>>
>>> 2013-10-20 Tom de Vries <tom@codesourcery.com>
>>>
>>> * gdb.arch/thumb2-it.S (it_8): Fix typo.
>>
>> OK.
>>
>
> Pedro,
>
> Thanks. I've tried to commit using cvs and got:
> ...
> $ cvs commit -F ./thumb2-it-typo.log gdb/testsuite
> ...
> binutils and gdb have migrated to git
> cvs commit: Pre-commit check failed
> binutils and gdb have migrated to git
> cvs commit: Pre-commit check failed
> cvs [commit aborted]: correct above errors first!
> ...
>
> I suspect cvs is the way to apply since http://www.sourceware.org/gdb/current
> says git is read-only. I suppose this error is due to lack of permissions.
>
> I'd be happy to have checkin permissions, and to apply myself.
>
> Otherwise, can you apply?
The GDB and binutils repositories (a.k.a. CVS "src" repo) is being
migrated to git right now.
https://sourceware.org/ml/gdb/2013-10/msg00068.html
The commit has been disabled until the migration finishes.
--
Sergio
prev parent reply other threads:[~2013-10-21 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 13:55 Tom de Vries
2013-10-21 14:51 ` Pedro Alves
2013-10-21 15:25 ` Tom de Vries
2013-10-21 15:33 ` Andreas Schwab
2013-10-21 15:37 ` Sergio Durigan Junior [this message]
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=m3sivuab50.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=Tom_deVries@mentor.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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