git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Zack Rusin <zack@kde.org>, git@vger.kernel.org
Subject: Re: Git cheat sheet
Date: Wed, 29 Aug 2007 10:32:24 +0200	[thread overview]
Message-ID: <vpqk5repwpz.fsf@bauges.imag.fr> (raw)
In-Reply-To: <7vfy22squc.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Wed\, 29 Aug 2007 01\:11\:07 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Zack Rusin <zack@kde.org> writes:
>
>> http://ktown.kde.org/~zrusin/git/git-cheat-sheet.svg
>
> Nice drawing 

True!

> and no typo.

Except for the blue closing parenthesis for (git-config --help), while
the opening one is black ;-).

> + "git commit" is not about publishing at all.

It does not publish in itself, but it's mostly necessary in order to
publish. For a short summary, I think it's OK to have it in the
publishing section, as long as it's just before "format-patch" and
"push".

otherwise, about the suggested flow on the top right, I'd move
"commit" to the left. Most of the time, "commit" comes before pull or
fetch. It normally comes before "revert", but after "reset" (revert
creates a new commit, you want to do it from a clean tree, so either
reset or commit before).

-- 
Matthieu

  reply	other threads:[~2007-08-29  8:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29  7:48 Git cheat sheet Zack Rusin
2007-08-29  7:46 ` Rene Herman
2007-08-29  8:11 ` Junio C Hamano
2007-08-29  8:32   ` Matthieu Moy [this message]
2007-08-29 10:04   ` Karl Hasselström
2007-08-29 12:55   ` Zack Rusin
2007-08-29 13:47     ` Dan Chokola
2007-08-29 16:14     ` Matthieu Moy
2007-08-29 23:37   ` Bernt Hansen
2007-08-30  4:05   ` Bernt Hansen
2007-08-29  9:34 ` Nguyen Thai Ngoc Duy
2007-08-30 23:49 ` Dan Zwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpqk5repwpz.fsf@bauges.imag.fr \
    --to=matthieu.moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=zack@kde.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).