Git Product home page Git Product logo

git.github.io's Introduction

Build status

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

git.github.io's People

Contributors

brunofbrito avatar chriscool avatar cogito avatar derrickstolee avatar dpursehouse avatar dscho avatar felipec avatar gaalcaras avatar gitster avatar jnareb avatar larsxschneider avatar lucamilanesio avatar matheustavares avatar mhagger avatar mjaix avatar moy avatar newren avatar omkarsonawane1230 avatar peff avatar phil-blain avatar philipoakley avatar rtyley avatar serjan-nasredin avatar sivaraam avatar stefanbeller avatar stepnem avatar tfnico avatar tgummerer avatar ttaylorr avatar vdye avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

git.github.io's Issues

Jekyll 3.0 related warning

I got the following warning after editing rn-12:

Subject: [git/git.github.io] Page build warning

The page build completed successfully, but returned the following warning:

You are currently using the 'redcarpet' Markdown engine, which will not be supported on GitHub Pages after May 1st. At that time, your site will use 'kramdown' for markdown rendering instead. To suppress this warning, remove the 'markdown' setting in your site's '_config.yml' file and confirm your site renders as expected. For more information, see https://help.github.com/articles/updating-your-markdown-processor-to-kramdown.

GitHub Pages was recently upgraded to Jekyll 3.0. It may help to confirm you're using the correct dependencies:

  https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0

For information on troubleshooting Jekyll see:

  https://help.github.com/articles/using-jekyll-with-pages#troubleshooting

If you have any questions you can contact us by replying to this email.

It looks like we should try removing the 'markdown' setting from the '_config.yml' file.

Compile Error on Git 2.0.1 on Redhat 5.9 with Fix

When compiling Git 2.0.1 on RedHat 5.9 as a non-root user I get the following error:

BUILD ERROR

make prefix=/home/eldon/local all doc info
...
    CC zlib.o
    CC unix-socket.o
    CC thread-utils.o
    CC compat/strlcpy.o
    AR libgit.a
/bin/sh: gar: command not found
make: *** [libgit.a] Error 127

My fix was to make a symlink below:

SYMLINK

gar -> /usr/bin/ar

LINUX VERSION

> lsb_release -i -r
Distributor ID: RedHatEnterpriseClient
Release:        5.9

I think the fix is to allow the use of "ar" if "gar" does not exist. I don't know if this exists for every Redhat install but "gar" is not available in /usr/bin but "ar" (which does exist in Redhat) does.

> /usr/bin/ar --version
GNU ar 2.17.50.0.6-20.el5_8.3 20061020
Copyright 2005 Free Software Foundation, Inc.

Broken Links in Git Rev News

Introductory text of git.github.io/rev_news reads like so: """Git Rev News: Edition 15 (May 11th, 2016)
Welcome to the 15th edition of Git Rev News, a digest of all things Git. For our goals, the archives, the way we work, and how to contribute or to subscribe, see the Git Rev News page on git.github.io.

This edition covers what happened during the month of April 2016, especially at the Git Contributor Summit on April 4 2016 and at the Git Merge conference on April 5 2016."""

Among three links, two of them go non-existent pages ("Git Rev News", and "Git Rev News page").

Gmane bugs and outages

I spend a lot of time these days to try to overcome gmane bugs or outages.

This is a problem because until now we have been using mostly gmane links especially for links from article titles to the discussion thread.

The last problem I had yesterday with gmane is that the following thread is missing some messages:

http://thread.gmane.org/gmane.comp.version-control.git/281254/

For example it is missing this message:

http://article.gmane.org/gmane.comp.version-control.git/281323/

I would have liked to write an article about this thread, but I didn't want to use a link to a broken thread on gmane, so I eventually chose another thread to write about.

rev_news: twitter

Some readers probably prefer "subscribing" by following on Twitter (atleast my podcast gathered a few hundred followers there). Who's for opening a @gitrevnews Twitter account? (as in: I'll do it unless there are objections)

cc @durdn @chriscool

Broken links all around

It seems at some point the Jekyll/GitHub Pages thingie broke our links. Basically everywhere where we link to something rev_news/rev_news.html, it breaks on GitHub, but not when running locally with Jekyll. I'm not sure if this is a configuration issue, or some limitation in GitHub pages, but it's too late in the evening for me to fiddle with it now. Will have a look another day.

RevNews #2: do not forget to remove "Support" if it stays empty

As this issue is an "special edition", it is perfectly OK if there were nothing noteworthy to report in the "Support" section, but if that will be the end result (we may not know yet), please remove the section heading before the empty section (this comment applies to any other sections, but I think everything other than "Support" has some contents already).

https on git.github.io

GitHub Pages now officially support https, and we can start using to https:// links everywhere. We should probably mass-update existing links to use https.

Likewise, there's now a config option we can flip to redirect http traffic to https automatically. I can't think of a good reason not to do this, unless there's somebody who really has an http implementation that can't do https. That seems far-fetched to me in 2016. So modulo any objections, I'll do that soon in a day or two.

/cc @git/web

Git and file attributes

I have used git for a long time, I found that when I change file attributes as chmod 755 file, git will mark as modified,

It's wrong, because git should track modified time, not changed time, it does not change content of file,

I think we should change this behaviour.

Improve the top of the newsletter

I'd rather have just something shorter at the top of each edition that redirect to http://git.github.io/rev_news/rev_news.html more strongly for all the meta information. And in turn we could have more and better meta information, like a nicer signup, on http://git.github.io/rev_news/rev_news.html.

For example if I would rewrite edition 2, I would only write something like (without showing the links) at the top:

Git Rev News: Edition 2 (April 15, 2015), 10 years of Git & Git Merge 2015!

Welcome to the second edition of Git Rev News, a digest of all things Git.
For our goals, the archives, the way we work, how to contribute or to
subscribe see the Git Rev News page on http://git.github.io.

This special edition covers Git's 10th year of existence, as well as the Git
Merge conference held on April 8th & 9th in Paris, France. Git developers
and users alike came together to celebrate the anniversary, and to discuss
the current challenges of using and scaling Git.

Discussions

General

10 years of fun

...

Mailing list for Rev News

It would be useful for people interested in this publication to be able to subscribe to it via email.

There was some interest shown on hacker news - https://news.ycombinator.com/item?id=9264924

At the very least, letting people know how they can get new issues when they are released is important, even better if they can sign up to a list while reading an issue.

Have a stable URL that always points at the latest edition

I was updating the MaintNotes and wanted to advertise the rev-news, but I had to spell the current one like this:

There is a volunteer-run newsletter to serve our community
(http://git.github.io/rev_news/edition-1.html). If you want to help
its publication, please contact Christian and/or Thomas.

which is way suboptimal. By the time I send it the next time, edition-1 would be stale, and
http://git.github.io/rev_news/ will just give us a 404.

MailChimp

I sent edition 19 using MailChimp but I did not use the template that Nicola had saved.
I tried it but it looked like the result had lost some formatting.
So instead I just used a new template where I just copied the HTML from the web page (https://git.github.io/rev_news/2016/09/14/edition-19/).

The main problem is that the background was white instead of brown. But otherwise the formatting looked better.

It would be nice to find a better solution to have both a good background and proper formatting.

rev_news: developer spotlight

Thanks to @gitster for this idea.

We could highlight some Git contributor in each edition. Hopefully we can have the first already in ed. 2 (#29).

Some example questions:

  • Who are you, and what do you do?
  • What would you name your most important contribution to Git?
  • What are you doing on the Git project these days, and why?
  • If you could get a team of expert developers to work full time on something in Git for a full year, what would it be?
  • If you could remove something from Git without worrying about backwards compatibility, what would it be?
  • What is your favorite Git-related tool/library, outside of Git itself?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.