Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAJS6+b5ydMhVa2N=aU0Rt0+=9NVjkP--43qafqyN32O2+E8+3A@mail.gmail.com>
References: 
 <CALwhT96rW2+K7Zy=RN5A7Fh-WAUAjshY-mg6H08JE+qi4KPUVw@mail.gmail.com>
	<CALwhT97_jaz2Tgf3rXNo50A09y-E9HyW0ZQx8p8i3zsyMzqJyw@mail.gmail.com>
	<CALwhT97yJ7jGynFJMuq4ZsD=tJO6jBxf=kQhiYoNAC=QuKuDbw@mail.gmail.com>
	<CA+4kjVuq4mWV=5cSP7TLq2V1e4NdgPtOUrOyhCUN9mAxWbAgSw@mail.gmail.com>
	<CALwhT97p8XzWMWJmZak_VY_88Yy6g=ns1E795ctV1bP9FGYLqw@mail.gmail.com>
	<CAJS6+b5ydMhVa2N=aU0Rt0+=9NVjkP--43qafqyN32O2+E8+3A@mail.gmail.com>
Date: Mon, 25 Aug 2014 16:35:33 -0700
Message-ID: 
 <CAH3-CVwaBEr=QVSrJ0T-Po5AS5yWw7ODLRSnLU8NwiE9s2agTA@mail.gmail.com>
Subject: Re: Updates on migration to git
From: Allen Wittenauer <aw@altiscale.com>
To: mapreduce-dev@hadoop.apache.org
Cc: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=001a11c351a0a3c1a105017ca47c

--001a11c351a0a3c1a105017ca47c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

RE: =E2=80=94author

No, we should not do this.  This just increases friction. It=E2=80=99s hard=
 enough
getting patches reviewed and committed, esp if you are not @apache.org.
Trying to dig up a valid address (nevermind potentially having to deal with
'nsfw12@example.com') is just asking for trouble.

Plus, the JIRA has the record.


On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen <zshen@hortonworks.com> wrote=
:

> Do we have any convention about "user.name" and "user.email"? For example=
,
> we'd like to use @apache.org for the email.
>
> Moreover, do we want to use "--author=3D"Author Name <email@address.com>"
> when committing on behalf of a particular contributor?
>
>
> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla <kasha@cloudera.com>
> wrote:
>
> > Thanks for your input, Steve. Sorry for sending the email out that late=
,
> I
> > sent it as soon as I could.
> >
> >
> > On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran <stevel@hortonworks.com=
>
> > wrote:
> >
> > > just caught up with this after some offlininess...15:48 PST is too la=
te
> > for
> > > me.
> > >
> > > I'd be -1 to a change to "master" because of that risk that it does
> break
> > > existing code -especially people that have trunk off the git mirrors
> and
> > > automated builds/merges to go with it.
> > >
> >
> > Fair enough. It makes sense to leave it as "trunk", unless someone is
> > against it being trunk.
> >
> >
> > >
> > > "master" may be viewed as the official git way, but it doesn't have t=
o
> > be.
> > > For git-flow workflows (which we use in slider) master/ is for
> releases,
> > > develop/ for dev.
> > >
> > >
> > >
> > >
> > > On 24 August 2014 02:31, Karthik Kambatla <kasha@cloudera.com> wrote:
> > >
> > > > Couple of things:
> > > >
> > > > 1. Since no one expressed any reservations against doing this on
> Sunday
> > > or
> > > > renaming trunk to master, I ll go ahead and confirm that. I think
> that
> > > > serves us better in the long run.
> > > >
> > > > 2. Arpit brought up the precommit builds - we should definitely fix
> > them
> > > as
> > > > soon as we can. I understand Giri maintains those builds, do we hav=
e
> > > anyone
> > > > else who has access in case Giri is not reachable? Giri - please
> shout
> > > out
> > > > if you can help us with this either on Sunday or Monday.
> > > >
> > > > Thanks
> > > > Karthik
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, Aug 22, 2014 at 3:50 PM, Karthik Kambatla <
> kasha@cloudera.com>
> > > > wrote:
> > > >
> > > > > Also, does anyone know what we use for integration between JIRA a=
nd
> > > svn?
> > > > I
> > > > > am assuming svn2jira.
> > > > >
> > > > >
> > > > > On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla <
> > kasha@cloudera.com>
> > > > > wrote:
> > > > >
> > > > >> Hi folks,
> > > > >>
> > > > >> For the SCM migration, feel free to follow
> > > > >> https://issues.apache.org/jira/browse/INFRA-8195
> > > > >>
> > > > >> Most of this is planned to be handled this Sunday. As a result,
> the
> > > > >> subversion repository would be read-only. If this is a major iss=
ue
> > for
> > > > you,
> > > > >> please shout out.
> > > > >>
> > > > >> Daniel Gruno, the one helping us with the migration, was asking =
if
> > we
> > > > are
> > > > >> open to renaming "trunk" to "master" to better conform to git
> > lingo. I
> > > > am
> > > > >> tempted to say yes, but wanted to check.
> > > > >>
> > > > >> Would greatly appreciate any help with checking the git repo has
> > > > >> everything.
> > > > >>
> > > > >> Thanks
> > > > >> Karthik
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> > > --
> > > CONFIDENTIALITY NOTICE
> > > NOTICE: This message is intended for the use of the individual or
> entity
> > to
> > > which it is addressed and may contain information that is confidentia=
l,
> > > privileged and exempt from disclosure under applicable law. If the
> reader
> > > of this message is not the intended recipient, you are hereby notifie=
d
> > that
> > > any printing, copying, dissemination, distribution, disclosure or
> > > forwarding of this communication is strictly prohibited. If you have
> > > received this communication in error, please contact the sender
> > immediately
> > > and delete it from your system. Thank You.
> > >
> >
>
>
>
> --
> Zhijie Shen
> Hortonworks Inc.
> http://hortonworks.com/
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity =
to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified th=
at
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediate=
ly
> and delete it from your system. Thank You.
>

--001a11c351a0a3c1a105017ca47c--