public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org, Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [python] [commit] Remove custom installation/configuration
Date: Fri, 07 Jan 2011 14:37:00 -0000	[thread overview]
Message-ID: <m3lj2wok48.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110107071407.GA2120@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Fri, 7 Jan 2011 08:14:07 +0100")

Jan> feel free to revert/modify/etc., I just thought it is OK for commit.

Definitely; thanks for doing that.
I looked at the diff yesterday and there were some minor things (decl
reordering and whitespace changes) that I think we should also sync with
master... that way it will be more clear what remains to upstream.
I'll do that now if they are still there.

Tom

      reply	other threads:[~2011-01-07 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07  7:14 Jan Kratochvil
2011-01-07 14:37 ` Tom Tromey [this message]

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=m3lj2wok48.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).