Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Gutson <daniel.gutson@tallertechnologies.com>
To: Doug Evans <dje@google.com>
Cc: gdb <gdb@sourceware.org>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: specifying gdb's exit code
Date: Tue, 22 Apr 2014 12:37:00 -0000	[thread overview]
Message-ID: <CAF5HaEX6BX6hfFwBkU_8xiHMxdK1Y9S44OZmUsnxpc7+cojsRw@mail.gmail.com> (raw)
In-Reply-To: <CAF5HaEX1jfUdDkH3FrNviGYezWog5oyVF3WYM6mwmP=EtrvCjQ@mail.gmail.com>

ping for micro and trivial patch.

(though I'm not sure if I should re-generate the .po files?)

On Thu, Apr 17, 2014 at 6:51 PM, Daniel Gutson
<daniel.gutson@tallertechnologies.com> wrote:
> What about this?
> (I'm not a native English speaker)
>
> If OK, please commit it for me since I don't have write-access.
>
> Thanks!
>
>     Daniel.
>
> 2014-04-17  Daniel Gutson  <daniel.gutson@tallertechnologies.com>
>
> gdb/cli/
>         * cli-cmds.c (_initialize_cli_cmds): Improve help message for
> the quit command.
>
> On Thu, Apr 17, 2014 at 6:34 PM, Daniel Gutson
> <daniel.gutson@tallertechnologies.com> wrote:
>> On Thu, Apr 17, 2014 at 6:32 PM, Doug Evans <dje@google.com> wrote:
>>> On Thu, Apr 17, 2014 at 12:08 PM, Daniel Gutson
>>> <daniel.gutson@tallertechnologies.com> wrote:
>>>> Sorry. Please ignore this email.
>>>>
>>>> I just noticed that "quit" already accepts an argument.
>>>
>>> Heh.
>>> IWBN if "help quit" pointed this out though.
>>
>> I thought the same, since that was the first thing I did (help quit
>> and apropos exit),
>> it would have helped.
>> I'll fix the help and send the patch.
>>
>> --
>>
>> Daniel F. Gutson
>> Chief Engineering Officer, SPD
>>
>>
>> San Lorenzo 47, 3rd Floor, Office 5
>>
>> Córdoba, Argentina
>>
>>
>> Phone: +54 351 4217888 / +54 351 4218211
>>
>> Skype: dgutson
>
>
>
> --
>
> Daniel F. Gutson
> Chief Engineering Officer, SPD
>
>
> San Lorenzo 47, 3rd Floor, Office 5
>
> Córdoba, Argentina
>
>
> Phone: +54 351 4217888 / +54 351 4218211
>
> Skype: dgutson



-- 

Daniel F. Gutson
Chief Engineering Officer, SPD


San Lorenzo 47, 3rd Floor, Office 5

Córdoba, Argentina


Phone: +54 351 4217888 / +54 351 4218211

Skype: dgutson


  reply	other threads:[~2014-04-22 12:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF5HaEVTZAxc0FNR9GnGNKJqxGSrbQaTfZ7ZRMoueTg6jQyL8A@mail.gmail.com>
     [not found] ` <CAF5HaEWDv6Gb2m-iDpzcM4y_ybkT46R1b96xxdS9buLHbsgwRQ@mail.gmail.com>
     [not found]   ` <CADPb22RS0J3X8hcBiUiDPp62RYiKPE4vCSPV5WEMUF01KzsiLg@mail.gmail.com>
     [not found]     ` <CAF5HaEV3wMHXfk3jLmbY-E6XAaZSmBRhzDjo2BvhQ7NbvvCtZQ@mail.gmail.com>
2014-04-17 21:52       ` Daniel Gutson
2014-04-22 12:37         ` Daniel Gutson [this message]
2014-04-23 17:11         ` Tom Tromey
2014-04-23 17:29           ` Eli Zaretskii
2014-04-23 17:29           ` Pedro Alves
2014-04-23 17:36             ` Paul_Koning
2014-04-23 17:46               ` Pedro Alves
2014-04-23 17:49             ` Tom Tromey
2014-04-23 17:57               ` Pedro Alves
2014-04-25 15:44                 ` Tom Tromey
2014-04-23 18:17               ` Paul_Koning
2014-04-23 18:23                 ` Tom Tromey
2014-04-23 20:53                   ` Daniel Gutson
2014-04-23 20:55                     ` Daniel Gutson

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=CAF5HaEX6BX6hfFwBkU_8xiHMxdK1Y9S44OZmUsnxpc7+cojsRw@mail.gmail.com \
    --to=daniel.gutson@tallertechnologies.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --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