Thanks for making this happen, Karthik and Daniel. Great job.
best,
Colin
On Tue, Aug 26, 2014 at 5:59 PM, Karthik Kambatla wrote:
> Yes, we have requested for force-push disabled on trunk and branch-*
> branches. I didn't test it though :P, it is not writable yet.
>
>
> On Tue, Aug 26, 2014 at
Yes, we have requested for force-push disabled on trunk and branch-*
branches. I didn't test it though :P, it is not writable yet.
On Tue, Aug 26, 2014 at 5:48 PM, Todd Lipcon wrote:
> Hey Karthik,
>
> Just to confirm, have we disabled force-push support on the repo?
>
> In my experience, espec
Hey Karthik,
Just to confirm, have we disabled force-push support on the repo?
In my experience, especially when a project has committers new to git,
force-push support causes more trouble than it's worth.
-Todd
On Tue, Aug 26, 2014 at 4:39 PM, Karthik Kambatla
wrote:
> Looks like our git re
Looks like our git repo is good to go.
On INFRA-8195, I am asking Daniel to enable writing to it. In case you find
any issues, please comment on the JIRA.
Thanks
Karthik
On Tue, Aug 26, 2014 at 3:28 PM, Arpit Agarwal
wrote:
> I cloned the new repo, built trunk and branch-2, verified all the b
I cloned the new repo, built trunk and branch-2, verified all the branches
are present. Also checked a few branches and the recent commit history
matches our existing repo. Everything looks good so far.
On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla
wrote:
> The git repository is now ready f
:) I missed that voting thread. Thanks Karthik!
Arpit Agarwal also told me offline that commit process has been updated -
https://wiki.apache.org/hadoop/HowToCommit and git setup also has also been
documented - https://www.apache.org/dev/git.html. Thanks Arpit!
On Tue, Aug 26, 2014 at 11:41 AM,
Did a build. Started some stuff. Have a patch ready to be committed. ;)
Thanks Karthik and Daniel!
On Aug 26, 2014, at 2:26 PM, Karthik Kambatla wrote:
> I compared the new asf git repo against the svn and github repos (mirrored
> from svn). Here is what I see:
> - for i in *; do git diff $i
I've just did some work on top of trunk and branch-2, all good.
Thanks Karthik.
On Tue, Aug 26, 2014 at 2:26 PM, Karthik Kambatla
wrote:
> I compared the new asf git repo against the svn and github repos (mirrored
> from svn). Here is what I see:
> - for i in *; do git diff $i ../hadoop-githu
I compared the new asf git repo against the svn and github repos (mirrored
from svn). Here is what I see:
- for i in *; do git diff $i ../hadoop-github/$i; done showed no
differences between the two. So, I think all the source is there.
- The branches match
- All svn tags exist in git, but git has
Hi,
Great to see the move towards git.
In terms of documentation could you please include the way binary files
should be included in a patch (see this discussion
https://www.mail-archive.com/common-dev%40hadoop.apache.org/msg13166.html )
and update http://wiki.apache.org/hadoop/GitAndHadoop too (
The git repository is now ready for inspection. I ll take a look shortly,
but it would be great if a few others could too.
Once we are okay with it, we can ask it to be writable.
On Tuesday, August 26, 2014, Karthik Kambatla wrote:
> Hi Suresh
>
> There was one vote thread on whether to migrate
Hi Suresh
There was one vote thread on whether to migrate to git, and the
implications to the commit process for individual patches and feature
branches -
https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html .
Prior to that, there was a discuss thread on the same topic.
As INFR
Karthik,
I would like to see detailed information on how this migration will be
done, how it will affect the existing project and commit process. This
should be done in a document that can be reviewed instead of in an email
thread on an ad-hoc basis. Was there any voting on this in PMC and should
Last I heard, the import is still going on and appears closer to getting
done. Thanks for your patience with the migration.
I ll update you as and when there is something. Eventually, the git repo
should be at the location in the wiki.
On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla
wrote:
>
On 25 August 2014 23:45, Karthik Kambatla wrote:
> Thanks for bringing these points up, Zhijie.
>
> By the way, a revised How-to-commit wiki is at:
> https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to
> make changes and improve it.
>
>
looks good so far
I suspect we'll evolv
RE: —author
No, we should not do this. This just increases friction. It’s 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
'nsf...@example.com') is just asking for trouble.
Plus, the JI
some of this info is here
https://git-wip-us.apache.org/
On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla
wrote:
> Thanks for bringing these points up, Zhijie.
>
> By the way, a revised How-to-commit wiki is at:
> https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to
> make
Thanks for bringing these points up, Zhijie.
By the way, a revised How-to-commit wiki is at:
https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to
make changes and improve it.
On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen wrote:
> Do we have any convention about "user.name" an
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="Author Name "
when committing on behalf of a particular contributor?
On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla
wrote:
> Thanks f
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
wrote:
> just caught up with this after some offlininess...15:48 PST is too late for
> me.
>
> I'd be -1 to a change to "master" because of that
just caught up with this after some offlininess...15:48 PST is too late 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.
"master" may be viewed as the o
Thanks Giri.
By the way, writes to svn are now disabled.
On Saturday, August 23, 2014, Giridharan Kesavan
wrote:
> I can take a look at this on Monday.
>
> -giri
>
>
> On Sat, Aug 23, 2014 at 6:31 PM, Karthik Kambatla >
> wrote:
>
> > Couple of things:
> >
> > 1. Since no one expressed any
I can take a look at this on Monday.
-giri
On Sat, Aug 23, 2014 at 6:31 PM, Karthik Kambatla
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
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 under
Also, does anyone know what we use for integration between JIRA and svn? I
am assuming svn2jira.
On Fri, Aug 22, 2014 at 3:48 PM, Karthik Kambatla
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
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 issue for you,
please shout out.
Daniel Gruno, the one helping us
26 matches
Mail list logo
