All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Zwell <dzwell@gmail.com>
To: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Cc: Zack Rusin <zack@kde.org>
Subject: Re: Git cheat sheet
Date: Thu, 30 Aug 2007 19:49:43 -0400	[thread overview]
Message-ID: <46D75797.8010007@gmail.com> (raw)
In-Reply-To: <200708290348.02853.zack@kde.org>

Zack Rusin wrote:
> Hey, 
> 
> I took a short break from being insanely handsome (which takes a lot of my 
> time - gorgeous doesn't just happen) and based on similar work for Mercurial 
> created a little SVG cheat sheet for Git.
...
> The SVG is at:
> http://ktown.kde.org/~zrusin/git/git-cheat-sheet.svg
> Sample png's are here:
> http://ktown.kde.org/~zrusin/git/git-cheat-sheet-medium.png
> http://ktown.kde.org/~zrusin/git/git-cheat-sheet-large.png
> 

I noticed that the cheat sheet listed the options "--theirs", "--ours", 
and "--base" for git-diff. These aren't in git-diff's manpage. A little 
grep-fu showed me that these are options of git-diff-files, but 
shouldn't they be documented with the porcelain, if the porcelain 
accepts them as options? (I normally use a text editor to view and 
resolve conflicts, but the presence of these options on a cheat sheet 
indicates that they are somewhat important.)

Thanks,
Dan

      parent reply	other threads:[~2007-08-30 23:50 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
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 [this message]

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=46D75797.8010007@gmail.com \
    --to=dzwell@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.