{"thread":{"id":"40736","subject":"A note from the maintainer","startedAt":"2015-11-05T23:14:06Z","lastAt":"2015-11-06T17:38:15Z","messageCount":3,"participants":["Junio C Hamano","Xue Fuqiao"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"272981","messageId":"xmqqa8qs3upt.fsf@gitster.mtv.corp.google.com","threadId":"40736","inReplyTo":null,"subject":"A note from the maintainer","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2015-11-05T23:14:06Z","receivedAt":"2015-11-05T23:14:06Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Welcome to the Git development community.\n\nThis message is written by the maintainer and talks about how Git\nproject is managed, and how you can work with it.\n\n* Mailing list and the community\n\nThe development is primarily done on the Git mailing list. Help\nrequests, feature proposals, bug reports and patches should be sent to\nthe list address <git@vger.kernel.org>.  You don't have to be\nsubscribed to send messages.  The convention on the list is to keep\neverybody involved on Cc:, so it is unnecessary to say \"Please Cc: me,\nI am not subscribed\".\n\nBefore sending patches, please read Documentation/SubmittingPatches\nand Documentation/CodingGuidelines to familiarize yourself with the\nproject convention.\n\nIf you sent a patch and you did not hear any response from anybody for\nseveral days, it could be that your patch was totally uninteresting,\nbut it also is possible that it was simply lost in the noise.  Please\ndo not hesitate to send a reminder message in such a case.  Messages\ngetting lost in the noise may be a sign that those who can evaluate\nyour patch don't have enough mental/time bandwidth to process them\nright at the moment, and it often helps to wait until the list traffic\nbecomes calmer before sending such a reminder.\n\nThe list archive is available at a few public sites:\n\n        http://news.gmane.org/gmane.comp.version-control.git/\n        http://marc.theaimsgroup.com/?l=git\n        http://www.spinics.net/lists/git/\n\nFor those who prefer to read it over NNTP:\n\n        nntp://news.gmane.org/gmane.comp.version-control.git\n\nWhen you point at a message in a mailing list archive, using\ngmane is often the easiest to follow by readers, like this:\n\n        http://thread.gmane.org/gmane.comp.version-control.git/27/focus=217\n\nas it also allows people who subscribe to the mailing list as gmane\nnewsgroup to \"jump to\" the article.\n\nSome members of the development community can sometimes be found on\nthe #git and #git-devel IRC channels on Freenode.  Their logs are\navailable at:\n\n        http://colabti.org/irclogger/irclogger_log/git\n        http://colabti.org/irclogger/irclogger_log/git-devel\n\nThere is a volunteer-run newsletter to serve our community (\"Git Rev\nNews\" http://git.github.io/rev_news/rev_news.html).\n\nGit is a member project of software freedom conservancy, a non-profit\norganization (https://sfconservancy.org/).  To reach a committee of\nliaisons to the conservancy, contact them at <git@sfconservancy.org>.\n\n\n* Reporting bugs\n\nWhen you think git does not behave as you expect, please do not stop\nyour bug report with just \"git does not work\".  \"I used git in this\nway, but it did not work\" is not much better, neither is \"I used git\nin this way, and X happend, which is broken\".  It often is that git is\ncorrect to cause X happen in such a case, and it is your expectation\nthat is broken. People would not know what other result Y you expected\nto see instead of X, if you left it unsaid.\n\nPlease remember to always state\n\n - what you wanted to achieve;\n\n - what you did (the version of git and the command sequence to reproduce\n   the behavior);\n\n - what you saw happen (X above);\n\n - what you expected to see (Y above); and\n\n - how the last two are different.\n\nSee http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for further\nhints.\n\nIf you think you found a security-sensitive issue and want to disclose\nit to us without announcing it to wider public, please contact us at\nour security mailing list <git-security@googlegroups.com>.\n\n\n* Repositories, branches and documentation.\n\nMy public git.git repositories are at:\n\n  git://git.kernel.org/pub/scm/git/git.git/\n  https://kernel.googlesource.com/pub/scm/git/git\n  git://repo.or.cz/alt-git.git/\n  https://github.com/git/git/\n  git://git.sourceforge.jp/gitroot/git-core/git.git/\n  git://git-core.git.sourceforge.net/gitroot/git-core/git-core/\n\nA few web interfaces are found at:\n\n  http://git.kernel.org/cgit/git/git.git\n  https://kernel.googlesource.com/pub/scm/git/git\n  http://repo.or.cz/w/alt-git.git\n\nPreformatted documentation from the tip of the \"master\" branch can be\nfound in:\n\n  git://git.kernel.org/pub/scm/git/git-{htmldocs,manpages}.git/\n  git://repo.or.cz/git-{htmldocs,manpages}.git/\n  https://github.com/gitster/git-{htmldocs,manpages}.git/\n\nAlso GitHub shows the manual pages formatted in HTML (with a\nformatting backend different from the one that is used to create the\nabove) at:\n\n  http://git-scm.com/docs/git\n\nThere are four branches in git.git repository that track the source tree\nof git: \"master\", \"maint\", \"next\", and \"pu\".\n\nThe \"master\" branch is meant to contain what are very well tested and\nready to be used in a production setting.  Every now and then, a\n\"feature release\" is cut from the tip of this branch.  They used to be\nnamed with three dotted decimal digits (e.g. \"1.8.5\"), but recently we\nswitched the versioning scheme and \"feature releases\" are named with\nthree-dotted decimal digits that ends with \".0\" (e.g. \"1.9.0\").\n\nThe last such release was 2.6.0 done on Sep 28th, 2015. You can expect\nthat the tip of the \"master\" branch is always more stable than any of\nthe released versions.\n\nWhenever a feature release is made, \"maint\" branch is forked off from\n\"master\" at that point.  Obvious, safe and urgent fixes after a\nfeature release are applied to this branch and maintenance releases\nare cut from it.  The maintenance releases used to be named with four\ndotted decimal, named after the feature release they are updates to\n(e.g. \"1.8.5.1\" was the first maintenance release for \"1.8.5\" feature\nrelease).  These days, maintenance releases are named by incrementing\nthe last digit of three-dotted decimal name (e.g. \"2.6.3\" is the\nthird maintenance release for the \"2.6\" series).\n\nNew features never go to the 'maint' branch.  This branch is also\nmerged into \"master\" to propagate the fixes forward as needed.\n\nA new development does not usually happen on \"master\". When you send a\nseries of patches, after review on the mailing list, a separate topic\nbranch is forked from the tip of \"master\" and your patches are queued\nthere, and kept out of \"master\" while people test it out. The quality of\ntopic branches are judged primarily by the mailing list discussions.\n\nTopic branches that are in good shape are merged to the \"next\" branch. In\ngeneral, the \"next\" branch always contains the tip of \"master\".  It might\nnot be quite rock-solid, but is expected to work more or less without major\nbreakage. The \"next\" branch is where new and exciting things take place. A\ntopic that is in \"next\" is expected to be polished to perfection before it\nis merged to \"master\".  Please help this process by building & using the\n\"next\" branch for your daily work, and reporting any new bugs you find to\nthe mailing list, before the breakage is merged down to the \"master\".\n\nThe \"pu\" (proposed updates) branch bundles all the remaining topic\nbranches the maintainer happens to have seen.  There is no guarantee that\nthe maintainer has enough bandwidth to pick up any and all topics that\nare remotely promising from the list traffic, so please do not read\ntoo much into a topic being on (or not on) the \"pu\" branch.  This\nbranch is mainly to remind the maintainer that the topics in them may\nturn out to be interesting when they are polished, nothing more.  The\ntopics on this branch aren't usually complete, well tested, or well\ndocumented and they often need further work.  When a topic that was\nin \"pu\" proves to be in a testable shape, it is merged to \"next\".\n\nYou can run \"git log --first-parent master..pu\" to see what topics are\ncurrently in flight.  Sometimes, an idea that looked promising turns out\nto be not so good and the topic can be dropped from \"pu\" in such a case.\n\nThe two branches \"master\" and \"maint\" are never rewound, and \"next\"\nusually will not be either.  After a feature release is made from\n\"master\", however, \"next\" will be rebuilt from the tip of \"master\"\nusing the topics that didn't make the cut in the feature release.\n\nNote that being in \"next\" is not a guarantee to appear in the next\nrelease, nor even in any future release.  There were cases that topics\nneeded reverting a few commits in them before graduating to \"master\",\nor a topic that already was in \"next\" was reverted from \"next\" because\nfatal flaws were found in it after it was merged to \"next\".\n\n\n* Other people's trees.\n\nDocumentation/SubmittingPatches outlines to whom your proposed changes\nshould be sent.  As described in contrib/README, I would delegate fixes\nand enhancements in contrib/ area to the primary contributors of them.\n\nAlthough the following are included in git.git repository, they have their\nown authoritative repository and maintainers:\n\n - git-gui/ comes from git-gui project, maintained by Pat Thoyts:\n\n        git://repo.or.cz/git-gui.git\n\n - gitk-git/ comes from Paul Mackerras's gitk project:\n\n        git://ozlabs.org/~paulus/gitk\n\n - po/ comes from the localization coordinator, Jiang Xin:\n\n\thttps://github.com/git-l10n/git-po/\n\nWhen sending proposed updates and fixes to these parts of the system,\nplease base your patches on these trees, not git.git (the former two\neven have different directory structures).\n"},{"id":"273007","messageId":"CAAF+z6Ea6CnDLgOsasUtJeYRVhHs6y+Tq3SdBy4JtDhNtoMH5Q@mail.gmail.com","threadId":"40736","inReplyTo":"xmqqa8qs3upt.fsf@gitster.mtv.corp.google.com","subject":"Re: A note from the maintainer","fromName":"Xue Fuqiao","fromEmail":"xfq.free@gmail.com","sentAt":"2015-11-06T10:50:31Z","receivedAt":"2015-11-06T10:50:31Z","isPatch":false,"sender":{"key":"xfq.free@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2863444?v=4"},"body":"Hi Junio,\n\nThanks for writing this note!  It is very helpful.\n\nOn Fri, Nov 6, 2015 at 7:14 AM, Junio C Hamano <gitster@pobox.com> wrote:\n> The list archive is available at a few public sites:\n>\n>         http://news.gmane.org/gmane.comp.version-control.git/\n>         http://marc.theaimsgroup.com/?l=git\n>         http://www.spinics.net/lists/git/\n\nThe second link is broken.  The following link is the correct version\nnow:\n\nhttps://marc.info/?l=git\n"},{"id":"273023","messageId":"xmqq1tc33u60.fsf@gitster.mtv.corp.google.com","threadId":"40736","inReplyTo":"CAAF+z6Ea6CnDLgOsasUtJeYRVhHs6y+Tq3SdBy4JtDhNtoMH5Q@mail.gmail.com","subject":"Re: A note from the maintainer","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2015-11-06T17:38:15Z","receivedAt":"2015-11-06T17:38:15Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thanks.  I've known about the URL moving to marc.info for a long\ntime, and I am kind of surprised that I had this stale one left\nun-updated for so long.\n\nFixed.\n"}]}