Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: async patch (no. 4)
Date: Fri, 12 Jan 2007 23:03:00 -0000	[thread overview]
Message-ID: <20070112230333.GA7039@nevyn.them.org> (raw)
In-Reply-To: <17832.2690.298735.867020@kahikatea.snap.net.nz>

On Sat, Jan 13, 2007 at 11:24:02AM +1300, Nick Roberts wrote:
>  > A problem I run into often at work is that when you try to merge
>  > another person's work, you often don't know how every bit of it works.
>  > But in order to review it, you've really got to figure out each
>  > line of it.  I try to read every line of my patch and ask myself
>  > why that line is right / necessary.
> 
> You're not looking at the last patch, which is smaller, that I sent:
> 
> Re: [PATCH] PR mi/2077 "set edit off" breaks MI"
> (Tue, 21 Nov 2006 11:20:41 +1300)

Whoops!  Thanks.  Well, let this be a reminder to both of us to put
things in their own threads :-)  I'll look at that one instead.  I
thought the other one was newer.

Thanks.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-01-12 23:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20  7:05 Nick Roberts
2007-01-12 18:31 ` Daniel Jacobowitz
2007-01-12 22:24   ` Nick Roberts
2007-01-12 23:03     ` Daniel Jacobowitz [this message]
2007-06-17  9:28       ` Nick Roberts
2007-06-17 15:21         ` Daniel Jacobowitz
2007-06-17 20:50           ` Nick Roberts
2007-06-18  2:46             ` Daniel Jacobowitz
2007-06-18  5:00               ` Nick Roberts
2007-06-18 11:32                 ` Daniel Jacobowitz
2007-06-18 21:48                   ` Nick Roberts

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=20070112230333.GA7039@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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