public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@hack.frob.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] ia64: move from main tree
Date: Mon, 16 Apr 2012 16:54:00 -0000	[thread overview]
Message-ID: <20120416165353.485442C099@topped-with-meat.com> (raw)
In-Reply-To: Mike Frysinger's message of  Sunday, 15 April 2012 22:37:17 -0400 <1334543837-828-1-git-send-email-vapier@gentoo.org>

I'm not going to review any of the ia64 content.  I'll just say that I
think this should be done with multiple commits, each with proper ChangeLog
bits.  First, just resurrect old files verbatim.  Then each of your bullet
items is a separate commit with normal detailed entries in ChangeLog.ia64.


Thanks,
Roland

  parent reply	other threads:[~2012-04-16 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  2:50 Mike Frysinger
2012-04-16  3:09 ` Mike Frysinger
2012-04-16 16:54 ` Roland McGrath [this message]
2012-04-16 18:04   ` Mike Frysinger
2012-04-16 18:06     ` Carlos O'Donell
2012-04-16 18:11     ` Roland McGrath
2012-04-16 18:13       ` Carlos O'Donell
2012-04-16 18:27       ` Mike Frysinger

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=20120416165353.485442C099@topped-with-meat.com \
    --to=roland@hack.frob.com \
    --cc=libc-ports@sourceware.org \
    --cc=vapier@gentoo.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).