Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 1/2] libunwind/ia64: Rename libunwind-frame.[ch]
Date: Tue, 06 Mar 2012 07:54:00 -0000	[thread overview]
Message-ID: <4F55C2BB.7090205@redhat.com> (raw)
In-Reply-To: <20120304215728.GA2763@host2.jankratochvil.net>

On 03/04/2012 09:57 PM, Jan Kratochvil wrote:

> Hi,
> 
> this is just a rename, it breaks the build, but it makes the changes
> reviewable in [patch 2/2].  It would be checked-in as a single commit.


BTW, there's a different way to split this so that you don't mix
the rename with other changes to the same files, and so that
git log sees through pure file renames without trouble.
That is, you rename the header in one patch, and rename the
c file in the other patch.  For example:

In patch #1 rename libunwind-frame.h -> ia64-tdep-libunwind-frame.h

but otherwise don't touch ia64-tdep-libunwind-frame.h.  Also do all
other adjustments to the other files so that the build doesn't break
(except for the build bits that need adjustment to compile
ia64-tdep-libunwind-frame.o instead).

In patch #2 rename libunwind-frame.c -> ia64-tdep-libunwind-frame.c

but otherwise don't touch ia64-tdep-libunwind-frame.c.  Do the
build bits adjustment to build ia64-tdep-libunwind-frame.o instead
in this patch.

Or the other way around, (there's more than one
way to split this).  The point is not to touch the same file
you're renaming in the same commit you're doing the rename in.

-- 
Pedro Alves


  reply	other threads:[~2012-03-06  7:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 21:58 Jan Kratochvil
2012-03-06  7:54 ` Pedro Alves [this message]
2012-03-06  8:43   ` Mark Kettenis
2012-03-06  8:45     ` Jan Kratochvil
2012-03-06  9:00     ` Tristan Gingold
2012-03-06  9:44       ` Pedro Alves
2012-03-06  9:53         ` Jan Kratochvil
2012-03-06 10:35           ` Pedro Alves
2012-03-06 10:48           ` Mark Kettenis
2012-03-06 11:32             ` Jan Kratochvil
2012-03-06 11:43               ` Pedro Alves
2012-03-08  9:15   ` Jan Kratochvil
2012-03-08 10:40     ` Pedro Alves

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=4F55C2BB.7090205@redhat.com \
    --to=palves@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