Return-Path: 
 <hdfs-dev-return-5123-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 99C0D7CD7
	for <apmail-hadoop-hdfs-dev-archive@minotaur.apache.org>;
 Fri, 23 Dec 2011 16:45:08 +0000 (UTC)
Received: (qmail 90442 invoked by uid 500); 23 Dec 2011 16:45:08 -0000
Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org
Received: (qmail 90375 invoked by uid 500); 23 Dec 2011 16:45:08 -0000
Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-dev@hadoop.apache.org>
List-Id: <hdfs-dev.hadoop.apache.org>
Reply-To: hdfs-dev@hadoop.apache.org
Delivered-To: mailing list hdfs-dev@hadoop.apache.org
Received: (qmail 90360 invoked by uid 99); 23 Dec 2011 16:45:08 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Dec 2011 16:45:08 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of praveensripati@gmail.com
 designates 209.85.215.176 as permitted sender)
Received: from [209.85.215.176] (HELO mail-ey0-f176.google.com)
 (209.85.215.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Dec 2011 16:45:01 +0000
Received: by eaac13 with SMTP id c13so12319890eaa.35
        for <multiple recipients>; Fri, 23 Dec 2011 08:44:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=J8b17VdVRsUJXF0R4ZJThxnLzaQ9p37Vblo1XiKwEvI=;
        b=DMGUWFIdgNCJlUhQAW22FhpQBt8E2jrVfjBpLw+7jBAO60bRC91wj71d3s6L4Zf6G3
         Ro7QLgELgI+CVz+1uKrECrkqhVpmfu6q68YaVMjx99psxVNlXnEMrpFhmMdFZeJ6N8NH
         vb+AiwycvadIjdVMlwjkvxSovZsDmHuBc3xnI=
MIME-Version: 1.0
Received: by 10.204.34.148 with SMTP id l20mr4314574bkd.55.1324658679962; Fri,
 23 Dec 2011 08:44:39 -0800 (PST)
Received: by 10.205.124.18 with HTTP; Fri, 23 Dec 2011 08:44:39 -0800 (PST)
Date: Fri, 23 Dec 2011 22:14:39 +0530
Message-ID: 
 <CADYHM8zxUsdMHRn36chx2tbMqSRkEStJ+7uT2E3L+oK3GrrRbw@mail.gmail.com>
Subject: Mapping between the JIRA and files changed
From: Praveen Sripati <praveensripati@gmail.com>
To: common-dev@hadoop.apache.org, hdfs-dev@hadoop.apache.org,
	mapreduce-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=000325559b16115c1904b4c52259

--000325559b16115c1904b4c52259
Content-Type: text/plain; charset=ISO-8859-1

Hi,

How do I know the code changed with a particular JIRA? If I go to
MAPREDUCE-1943, there are multiple patch attachments. Should I go with the
date and pick the latest patch?

Is there any other way to identify the changes done to the code with a
particular JIRA?

Regards,
Praveen

--000325559b16115c1904b4c52259--