git/gitscm-old

Git homepage that rocks - from the git.or.cz awesomeness

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-<commandname>.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to [email protected] (read Documentation/SubmittingPatches for instructions on patch submission and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email to [email protected] (see https://subspace.kernel.org/subscribing.html for details). The mailing list archives are available at https://lore.kernel.org/git/, https://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list [email protected].

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

• random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
• stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
• "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
• "goddamn idiotic truckload of sh*t": when it breaks

gitscm-old's Issues

learning git screencasts

some high quality getting started screencasts for git

incorporate pro git content or cross link

the pro git book content should be first class content on the site. search should link to it and links should return

man page / doc landing page

show all the man pages, grouped by function, linking to man page permalinks

man-page search

search bar should search through man-page titles and content

git urls on clone page should be bullets

If you look under "Git URLs" here:

http://git-scm.herokuapp.com/ref/git-clone

There are a bunch of url examples that are in a paragraph rather than bullets

incorporate gitref.org content

all the gitref.org content should be in git-scm

incorporate whygitisbetterthanx content

all the wgibtx content should be in git-scm, except remove the comparisons to the other dvcs systems and concentrate on the advantages of git over clearcase, perforce, svn

blog

we should have a blog - detailing new releases and what's in them, as well as pointing out interesting things in the git community

Incorporate new homepage design

Incorporate Jason's new homepage design.

bisect asciidoc rendering issue

near "# tweak the working tree" a bunch of formatting is off.

also link:git-bisect-lk2009.html[Fighting regressions with git bisect] is not rendered.

OSX Packages very confusing

From the git mailing list:

On Tue, Sep 20, 2011 at 3:40 PM, tom smitts [email protected] wrote:

Do the git maintainers really think any mac users have
 a clue which git install package to download?  You
put some arcane chipset designation in the package
 name!  Why make mac installers at all?  Mac users
know their operating system number, e.g. 10.6.7,
and that's all.  I doubt Windows users know any better.
And I doubt you can find anywhere on a mac that says
 i386 or whatever the heck the other dumb
designation is.

I definitely feel his pain, the link we use for the OSX binaries is confusing beyond belief. We should maybe cultivate a custom list of binaries?

update current version/man-page content via github api

poll the github git mirror git/git for new versions, add new versions and update which is the latest, then find man-page changes and store and index them

Redirect this repository to the new location

We have the technology. Say the word and I'll redirect this and github/gitscm-next to the canonical version at:

https://github.com/github/gitscm-next

Wide preformatted text cannot be viewed

See http://git-scm.herokuapp.com/docs/git-merge/1.7.10, the HOW CONFLICTS ARE PRESENTED section. The overly wide text is unviewable. I think the best thing to do would probably be to add a scrollbar if the content is too wide. Of course if the content is wide and tall then a single scrollbar at the bottom is really frustrating too...

make favicon of new logo

use new logo in more places:

whats dis

implement man-page browser design

use Jason's new man-page browser design

asciidoc *note* tag not parsing correctly

On the rebase page, if you compare this:

http://git-scm.herokuapp.com/ref/git-rebase

to this:

http://git-scm.blackantmedia.com/documentation/reference/rebase.html

There is a NOTE section that is not being parsed correctly.

auto man-page generator

need some way to find, pull and build man-page docs from source.

i would prefer to just do it from source too, in case junio decides not to publish the html branch anymore. back fill it with all old releases too.

git-config manpage 404ing

http://book.git-scm.com/5_customizing_git.html links to http://www.kernel.org/pub/software/scm/git/docs/git-config.html which is 404ing.

auto-download os specific version

we need to detect the user environment and offer in a single click the correct software to download, then possibly redirect to instructions on how to install it and get started. also possibly link to GUIs?

easy pro git content linking

easy to link to pro git content and permalinks

deprecate git community book

replace all urls with redirects to pro git or tutorial equivalents

mailing list browser

gmane is just goddamn awful.

have a sane email list interface for the git ML that is searchable through git-scm, filterable, permalinkable and possibly postable (perhaps authing through google or github)

build and maintain search database

scripts to fill and maintain elasticsearch db on heroku

search bar functionality

search bar should search through:

• command names
• man-pages (most recent first)
• pro-git book
• stack overflow questions (?)
• release notes (?)

it should look similar to this:

new wiki

the previous wiki was OK and a lot of people used it, but it's now dead due to k.org biting the bullet.

implement a new wiki interface and way to contribute super easily.

import the old wiki, too.

Commit access to gitscm

Can we please have more people with commit access to gitscm, pushing to gitscm.com?

There are 10 pull requests and 11 issues with a huge lag. gitscm.com seems to be the first place many people hit, so it should be up to date. It links to the "git community" (git mailing list) but it's hard for that community to get involved, the way it currently is.

The alternative is forking (again) and finding a new domain, of course, but let's not go there.