Return-Path: 
 <user-return-4833-apmail-flume-user-archive=flume.apache.org@flume.apache.org>
X-Original-To: apmail-flume-user-archive@www.apache.org
Delivered-To: apmail-flume-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1DBA2100A4
	for <apmail-flume-user-archive@www.apache.org>;
 Thu, 24 Oct 2013 19:42:27 +0000 (UTC)
Received: (qmail 92992 invoked by uid 500); 24 Oct 2013 19:40:18 -0000
Delivered-To: apmail-flume-user-archive@flume.apache.org
Received: (qmail 92929 invoked by uid 500); 24 Oct 2013 19:40:12 -0000
Mailing-List: contact user-help@flume.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@flume.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@flume.apache.org>
List-Post: <mailto:user@flume.apache.org>
List-Id: <user.flume.apache.org>
Reply-To: user@flume.apache.org
Delivered-To: mailing list user@flume.apache.org
Received: (qmail 92707 invoked by uid 99); 24 Oct 2013 19:39:56 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Oct 2013 19:39:56 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of hshreedharan@cloudera.com
 designates 209.85.220.52 as permitted sender)
Received: from [209.85.220.52] (HELO mail-pa0-f52.google.com) (209.85.220.52)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Oct 2013 19:39:49 +0000
Received: by mail-pa0-f52.google.com with SMTP id kl14so3688194pab.39
        for <user@flume.apache.org>; Thu, 24 Oct 2013 12:39:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to
         :references:subject:mime-version:content-type;
        bh=ovGr6gs9GILpPOG6zGzc+a9d1k/AQzH+FALaMvKZpOo=;
        b=cZEDGs85JPMFJU/2AJWYDaXQ4PTfPZnepJnE/VS35ZaomAGtyIdArSRLnwgXvO6UZP
         RWqYlVyQINXzDF4A+tsonXYV16WMSWugeVYkduZ6G09cMErpAWq7RQ0pU1qFkom9iUlw
         7D2/h8zM5hpF/ZSWDlSe5qDXWUF0imb0TCsqoBPI6U/m5VNOBPnLpy3P1maAcYl+WMep
         P6tlIv7ZeszEZ5wmCt3bpk3+Tuv1+vDQcYjSdioSmuiCOkGRnh6fdh133qsSF4JgYZpp
         EpnSy6e9VQGaI1hT0BlPEfKbsuKvuodNyvGd+M/efTsCh1Kc21gn9fBq8rcvRO4W95Yq
         0DiQ==
X-Gm-Message-State: 
 ALoCoQlaoqHgHTZLuD+h39goQHxAfOoAPaIaHAR6RkgwP/P4N2u75tETdERQTN4J2OL24WBrewbx
X-Received: by 10.66.4.105 with SMTP id j9mr4992514paj.84.1382643568103;
        Thu, 24 Oct 2013 12:39:28 -0700 (PDT)
Received: from [172.16.1.151] ([74.217.76.11])
        by mx.google.com with ESMTPSA id ed3sm4450982pbc.6.2013.10.24.12.39.26
        for <multiple recipients>
        (version=TLSv1 cipher=RC4-SHA bits=128/128);
        Thu, 24 Oct 2013 12:39:27 -0700 (PDT)
Date: Thu, 24 Oct 2013 12:39:25 -0700
From: Hari Shreedharan <hshreedharan@cloudera.com>
To: user@flume.apache.org
Cc: jlord@cloudera.com
Message-ID: <4F16C845067043F09C174C846A065776@cloudera.com>
In-Reply-To: 
 <CAKx7BGp8FHY9D=CT=h7orE-4ynF4xdo-CdaAZzMG2eM4Pncwzg@mail.gmail.com>
References: 
 <CAKx7BGp8FHY9D=CT=h7orE-4ynF4xdo-CdaAZzMG2eM4Pncwzg@mail.gmail.com>
Subject: Re: A quick question about committing patches to flume repo
X-Mailer: sparrow 1.6.4 (build 1178)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5269776d_41a7c4c9_b8"
X-Virus-Checked: Checked by ClamAV on apache.org

--5269776d_41a7c4c9_b8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Dib, 

Which patch is this? You will not be able to push to the repository - you will need to have a committer review it and then commit it for you.  


Thanks,
Hari


On Thursday, October 24, 2013 at 12:19 PM, Dibyajyoti Ghosh wrote:

> Hi all,
> 
> I have locally committed my patch with (my_name via Jeff Lord) in the commit message and about to do a git push origin trunk. 
> 
> I made sure that mvn clean install succeed with the patch applied and did testing with the patched JAR file in my local development environment. 
> 
> Should I go ahead and push the patch upstream in trunk as well as Flume-1.5 branch?
> 
> Thanks,
> - Dib
> 
> 
> 



--5269776d_41a7c4c9_b8
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


                <div>Hi Dib,
                </div><div><br></div><div>Which patch is this=3F You will=
 not be able to push to the repository - you will need to have a committe=
r review it and then commit it for you.&nbsp;</div>
                <div><div><br></div><br><div>Thanks,</div><div>Hari</div>=
<div><br></div></div>
                =20
                <p style=3D=22color: =23A0A0A8;=22>On Thursday, October 2=
4, 2013 at 12:19 PM, Dibyajyoti Ghosh wrote:</p>
                <blockquote type=3D=22cite=22 style=3D=22border-left-styl=
e:solid;border-width:1px;margin-left:0px;padding-left:10px;=22>
                    <span><div><div><div dir=3D=22ltr=22>Hi all,<div><br>=
</div><div>I have locally committed my patch with (my=5Fname via Jeff Lor=
d) in the commit message and about to do a git push origin trunk.&nbsp;</=
div><div><br></div><div>I made sure that mvn clean install succeed with t=
he patch applied and did testing with the patched JAR file in my local de=
velopment environment.</div>

<div><br></div><div>Should I go ahead and push the patch upstream in trun=
k as well as =46lume-1.5 branch=3F</div><div><br></div><div>Thanks,</div>=
<div>- Dib</div></div>
</div></div></span>
                =20
                =20
                =20
                =20
                </blockquote>
                =20
                <div>
                    <br>
                </div>
            
--5269776d_41a7c4c9_b8--