steveloughran commented on issue #1733: HADOOP-16735. Make it clearer in config default that EnvironmentVariableCredentialsProvider supports AWS_SESSION_TOKEN URL: https://github.com/apache/hadoop/pull/1733#issuecomment-561653910 multiple ways * through the UI. Can lose the author info. Make sure the commit message you get to fill-in includes the contributor name. (github signs these BTW, so add its key to your keychain) * Yetus smart-apply patch. Works well for trunk, mostly. As it applys the entire chain sometimes it has some problems. ``` dev-support/bin/smart-apply-patch --project=hadoop GH:1711 ``` Unless you use the option to commit the chain of patches (I don't) things are uncommitted. You should do the final commit yourself, ideally with a --author attribute to give the contributor credit across github, -S to GPG sign. * your own work: git diff, git apply etc. I do this sometimes when things are complex. Download the .patch file by adding .patch to the PR URL; apply ``` http -F https://github.com/apache/hadoop/pull/1388.patch > 1388.patch git apply < 1388.patch git add ... git commit -S --author "someone" ``` Then commit manually. For back porting I check out locally and then cherry pick. As this is your own work, just hit the squash and merge button and see how it goes. Except: why don't you have write access? Try from the command line with smart-apply-patch instead
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
