public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: jkratoch@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  jankratochvil/man: Merge branch 'gcore1-2' into jankratochvil/man
Date: Mon, 08 Apr 2013 17:24:00 -0000	[thread overview]
Message-ID: <20130408172409.3801.qmail@sourceware.org> (raw)

The branch, jankratochvil/man has been updated
       via  091729ae96e2e67bfb6d10818c4070776e0e90b6 (commit)
       via  6a4bf8bc4392cccad82f34ff49514212f01f7274 (commit)
       via  94d162ea3c59347579ab3824ddd39f149fc19e19 (commit)
      from  f9af973eb90da81361d6af3aec8d5eaffc2c5633 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit 091729ae96e2e67bfb6d10818c4070776e0e90b6
Merge: 94d162e 6a4bf8b
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Mon Apr 8 19:23:58 2013 +0200

    Merge branch 'gcore1-2' into jankratochvil/man

commit 6a4bf8bc4392cccad82f34ff49514212f01f7274
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Mon Apr 8 19:23:24 2013 +0200

    .

commit 94d162ea3c59347579ab3824ddd39f149fc19e19
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Mon Apr 8 19:23:24 2013 +0200

    .

-----------------------------------------------------------------------

Summary of changes:
 gdb/doc/gdb.texinfo |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

First 500 lines of diff:
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 20306a5..b43caeb 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -42150,9 +42150,9 @@ gcore [-o @var{filename}] @var{pid}
 @c man begin DESCRIPTION gcore
 Generate a core dump of a running program with process ID @var{pid}.
 Produced file is equivalent to a kernel produced core file as if the process
-crashed (and also it had to have @command{ulimit -c} enabled appropriately).
-Contrary to it after @command{gcore} the program remains running without any
-change.
+crashed (and if @kbd{ulimit -c} were used to set up an appropriate core dump
+limit).  Unlike after a crash, after @command{gcore} the program remains
+running without any change.
 @c man end
 
 @c man begin OPTIONS gcore


hooks/post-receive
--
Repository for Project Archer.


             reply	other threads:[~2013-04-08 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 17:24 jkratoch [this message]
2013-04-08 19:14 jkratoch

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=20130408172409.3801.qmail@sourceware.org \
    --to=jkratoch@sourceware.org \
    --cc=archer-commits@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).