検索

Results of 1 - 10 of about 21 for upstream (0.064 sec.)

Working with Git and GitHub — Django 4.0.6 ドキュメント 13716: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... n Git. You should also set up django/django as an "upstream" remote (that is, tell git that the reference Djan ... was the source of your fork of it): git remote add upstream https : // github . com / django / django . git gi ... t fetch upstream You can add other remotes similarly, for example: ... e a new branch for the work, and base that work on upstream/main : git checkout - b ticket_xxxxx upstream / ma ...; https://man.plustar.jp/django/internals/contributing/writing-code/working-with-g... - [similar]

コードのコミット — Django 4.0.6 ドキュメント 11619: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... s will be helpful: [alias] pr = !sh -c \"git fetch upstream pull/${1}/head:pr/${1} && git checkout pr/${1}\" A ... dd it to your ~/.gitconfig , and set upstream to be django/django . Then you can run git pr #### ... changes from main. $ git checkout main $ git pull upstream main $ # Rebase the pull request on main. $ git ch ... only the $ # changes you expect will be pushed to upstream. $ git push --dry-run upstream main $ # Push! $ gi ...; https://man.plustar.jp/django/internals/contributing/committing-code.html - [similar]

Django 3.1.14 release notes — Django 4.0.6 ドキュメント 10334: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... in 3.1.13. CVE-2021-44420: Potential bypass of an upstream access control based on URL paths ¶ HTTP requests ... for URLs with trailing newlines could bypass an upstream access control based on URL paths. 目次 Django 3.1 ... lease notes CVE-2021-44420: Potential bypass of an upstream access control based on URL paths 前のトピックへ D ... ーワード release , notes , paths , based , control , upstream , bypass , トピック , Potential , up クイック検索 ...; https://man.plustar.jp/django/releases/3.1.14.html - [similar]

Django 2.2.25 release notes — Django 4.0.6 ドキュメント 10266: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... in 2.2.24. CVE-2021-44420: Potential bypass of an upstream access control based on URL paths ¶ HTTP requests ... for URLs with trailing newlines could bypass an upstream access control based on URL paths. 目次 Django 2.2 ... lease notes CVE-2021-44420: Potential bypass of an upstream access control based on URL paths 前のトピックへ D ... ーワード release , notes , paths , based , control , upstream , bypass , トピック , Potential , up クイック検索 ...; https://man.plustar.jp/django/releases/2.2.25.html - [similar]

Django 3.2.10 release notes — Django 4.0.6 ドキュメント 10198: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... g in 3.2.9. CVE-2021-44420: Potential bypass of an upstream access control based on URL paths ¶ HTTP requests ... for URLs with trailing newlines could bypass an upstream access control based on URL paths. Bugfixes ¶ Fixe ... lease notes CVE-2021-44420: Potential bypass of an upstream access control based on URL paths Bugfixes 前のトピ ... ワード release , notes , bypass , based , control , upstream , paths , previous , トピック , Bugfixes クイック検 ...; https://man.plustar.jp/django/releases/3.2.10.html - [similar]

Django 1.8.8 リリースノート — Django 4.0.6 ドキュメント 7814: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... est subsequent releases against Python 3.2 either. Upstream support for Python 3.2 ends February 2016 so we do ...; https://man.plustar.jp/django/releases/1.8.8.html - [similar]

Django 1.8 リリースノート — Django 4.0.6 ドキュメント 7814: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... t release to support Python 3.5. Due to the end of upstream support for Python 3.2 in February 2016, we won't ... or PostgreSQL versions older than 9.0 ¶ The end of upstream support periods was reached in July 2014 for Postg ... ort for MySQL versions older than 5.5 ¶ The end of upstream support periods was reached in January 2012 for My ... t for Oracle versions older than 11.1 ¶ The end of upstream support periods was reached in July 2010 for Oracl ...; https://man.plustar.jp/django/releases/1.8.html - [similar]

Django 2.1 リリースノート — Django 4.0.6 ドキュメント 7814: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... ved. MySQL 5.5 に対するサポートの終了 ¶ The end of upstream support for MySQL 5.5 is December 2018. Django 2.1 ... PostgreSQL 9.3 に対するサポートの終了 ¶ The end of upstream support for PostgreSQL 9.3 is September 2018. Djan ...; https://man.plustar.jp/django/releases/2.1.html - [similar]

Django 4.0 release notes — Django 4.0.6 ドキュメント 7746: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... 5 is removed. Dropped support for PostgreSQL 9.6 ¶ Upstream support for PostgreSQL 9.6 ends in November 2021. ... hon 3.8. Dropped support for Oracle 12.2 and 18c ¶ Upstream support for Oracle 12.2 ends in March 2022 and for ...; https://man.plustar.jp/django/releases/4.0.html - [similar]

Django 3.0 リリースノート — Django 4.0.6 ドキュメント 7678: " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va ... tgreSQL 9.4 ¶ 2019年12月に PostgreSQL 9.4 に対する upstream のサポートが終了しました。これに伴い、Django 3.0 か ... 。 Dropped support for Oracle 12.1 ¶ Oracle 12.1 の upstream のサポートが2021年7月に終了します。Django2.2 は202 ...; https://man.plustar.jp/django/releases/3.0.html - [similar]

PREV 1 2 3 NEXT

Django ドキュメント