From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] bitpos expansion summary reloaded
Date: Fri, 28 Sep 2012 11:40:00 -0000 [thread overview]
Message-ID: <20120928170937.5f797857@spoyarek> (raw)
In-Reply-To: <20120928112024.GC22720@host2.jankratochvil.net>
On Fri, 28 Sep 2012 13:20:24 +0200, Jan wrote:
> Hi Siddhesh,
>
> is anywhere FSF GDB GIT commit hash which all this work is for?
cec90d9d386f57f116e114c50e4287281420f531
> On Thu, 27 Sep 2012 15:30:53 +0200, Siddhesh Poyarekar wrote:
> > I have also updated my repository of splint output reports here:
> >
> > http://git.siddhesh.in/cgit.cgi/splint.git/
>
> BTW I cannot "git clone" it. Possibly using downloads of each file
> from this web interface I see no logs or timestamps and there are too
> many files, most of which are probably no longer worth checking.
git clone http://git.siddhesh.in/splint.git
should work.
> So far I do not see how to review the patch as it is not annotated
> which change is for which valid splint warning. Comment from other
Oh I'm sorry, I thought you intended to do that as part of your review,
so I did not do it. The older warnings (processed) are in
splint-bitpos2.locdiff.processed and the new ones are in
splint-bitpos3.locdiff.processed. I generated the reports.done so that
you don't have to redo the earlier review.
Regards,
Siddhesh
next prev parent reply other threads:[~2012-09-28 11:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 13:33 Siddhesh Poyarekar
2012-09-28 11:20 ` Jan Kratochvil
2012-09-28 11:40 ` Siddhesh Poyarekar [this message]
2012-09-28 12:06 ` Jan Kratochvil
2012-09-28 12:19 ` Siddhesh Poyarekar
2012-09-29 17:39 ` Jan Kratochvil
2012-09-29 18:12 ` Jan Kratochvil
2012-09-30 6:52 ` Jan Kratochvil
2012-10-01 5:21 ` Siddhesh Poyarekar
2012-10-01 6:14 ` Jan Kratochvil
2012-10-03 13:12 ` Siddhesh Poyarekar
2012-10-03 18:38 ` Jan Kratochvil
2012-10-04 7:20 ` Siddhesh Poyarekar
2012-10-03 19:56 ` Jan Kratochvil
2012-10-04 7:13 ` Jan Kratochvil
2012-10-21 7:36 ` Siddhesh Poyarekar
2012-10-22 20:45 ` Tom Tromey
2012-10-23 1:34 ` Jan Kratochvil
2012-10-23 1:58 ` Jan Kratochvil
2012-10-23 2:29 ` Siddhesh Poyarekar
2012-10-23 2:37 ` Jan Kratochvil
2012-10-23 2:38 ` Tom Tromey
2012-10-23 19:11 ` Jan Kratochvil
2012-10-24 18:33 ` Tom Tromey
2012-10-24 18:55 ` Jan Kratochvil
2012-10-24 20:18 ` Tom Tromey
2012-10-25 15:54 ` Jan Kratochvil
2012-10-25 16:52 ` Siddhesh Poyarekar
2012-11-06 20:01 ` Jan Kratochvil
2012-11-07 13:48 ` Jan Kratochvil
2012-11-13 19:46 ` Tom Tromey
2012-11-13 19:55 ` Jan Kratochvil
2012-11-01 15:24 ` Jan Kratochvil
2012-11-01 16:56 ` Siddhesh Poyarekar
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=20120928170937.5f797857@spoyarek \
--to=siddhesh@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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