Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
From: rmetzger <git@git.apache.org>
To: issues@flink.incubator.apache.org
Reply-To: issues@flink.incubator.apache.org
Message-ID: <git-pr-786-flink@git.apache.org>
Subject: [GitHub] flink pull request: [FLINK-1126][docs] Best practice: named
 TupleX...
Content-Type: text/plain
Date: Thu,  4 Jun 2015 17:32:57 +0000 (UTC)

GitHub user rmetzger opened a pull request:

    https://github.com/apache/flink/pull/786

    [FLINK-1126][docs] Best practice: named TupleX types

    
You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rmetzger/flink flink1126

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/786.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #786
    
----
commit ce49d9c137d7542a7f5b214df85ff3093a3519f9
Author: Robert Metzger <rmetzger@apache.org>
Date:   2015-06-04T17:32:17Z

    [FLINK-1126][docs] Best practice: named TupleX types

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---