hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "GitAndHadoop" by ArpitAgarwal
Date Tue, 22 Nov 2016 18:47:14 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "GitAndHadoop" page has been changed by ArpitAgarwal:
https://wiki.apache.org/hadoop/GitAndHadoop?action=diff&rev1=24&rev2=25

Comment:
Remove some obsolete instructions

  
  == Forking onto GitHub ==
  
- You can create your own fork of the ASF project, put in branches and stuff as you desire.
GitHub prefer you to explicitly fork their copies of Hadoop.
+ You can create your own fork of the ASF project. This is required if you want to contribute
patches by submitting pull requests. However you can choose to skip this step and attach patch
files directly on Apache Jiras.
  
   1. Create a GitHub login at http://github.com/ ; Add your public SSH keys
+  1. Go to https://github.com/apache/hadoop/
+  1. Click fork in the github UI. This gives you your own repository URL.
-  1. Go to http://github.com/apache and search for the Hadoop and other Apache projects you
want (avro is handy alongside the others)
-  1. For each project, fork in the github UI. This gives you your own repository URL which
you can then clone locally with {{{git clone}}}
-  1. For each patch, branch.
- 
- At the time of writing (December 2009), GitHub was updating its copy of the Apache repositories
every hour. As the Apache repositories were updating every 15 minutes, provided these frequencies
are retained, a GitHub-fork derived version will be at worst 1 hour and 15 minutes behind
the ASF's Git repository. If you are actively developing on Hadoop, especially committing
code into the Git repository, that is too long -work off the Apache repositories instead.

- 
-  1. Clone the read-only repository from Github (their recommendation) or from Apache (the
ASF's recommendation)
-  1. in that clone, rename that repository "apache": {{{git remote rename origin apache}}}
-  1. Log in to [http://github.com]
-  1. Create a new repository (e.g hadoop-fork)
-  1. In the existing clone, add the new repository : 
+  1. In the existing clone, add the new repository: 
   {{{git remote add -f github git@github.com:MYUSERNAMEHERE/hadoop.git}}}
  
- This gives you a local repository with two remote repositories: "apache" and "github". Apache
has the trunk branch, which you can update whenever you want to get the latest ASF version:
+ This gives you a local repository with two remote repositories: {{{origin}}} and {{{github}}}.
{{{origin}}} has the Apache branches, which you can update whenever you want to get the latest
ASF version:
  
  {{{
-  git checkout trunk
-  git pull apache
+  git checkout -b trunk origin/trunk
+  git pull origin
  }}}
  
- Your own branches can be merged with trunk, and pushed out to git hub. To generate patches
for submitting as JIRA patches, check everything in to your specific branch, merge that with
(a recently pulled) trunk, then diff the two:
+ Your own branches can be merged with trunk, and pushed out to GitHub. To generate patches
for attaching to Apache JIRAs, check everything in to your specific branch, merge that with
(a recently pulled) trunk, then diff the two:
- {{{ git diff --no-prefix trunk > ../hadoop-patches/HADOOP-XYX.patch }}}
+ {{{ git diff trunk > ../hadoop-patches/HADOOP-XYX.patch }}}
- 
- If you are working deep in the code it's not only convenient to have a directory full of
patches to the JIRA issues, it's convenient to have that directory a git repository that is
pushed to a remote server, such as [[https://github.com/steveloughran/hadoop-patches|this
example]]. Why? It helps you move patches from machine to machine without having to do all
the updating and merging. From a pure-git perspective this is wrong: it loses history, but
for a mixed workflow it doesn't matter so much.
  
  
  == Branching ==

---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org


Mime
View raw message