From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: lilypond-devel@gnu.org
Subject: Re: git patch
Date: Wed, 06 Dec 2006 11:22:32 +0100 [thread overview]
Message-ID: <el65h9$tfj$2@sea.gmane.org> (raw)
In-Reply-To: 4576937D.1070402@xs4all.nl
Han-Wen Nienhuys wrote:
> I think it would be more logical to show those diffs as part of
> git-status and perhaps git-commit, eg.
>
> git-commit --dry-run <commitoptions>
>
> shows the diff of what would be committed
>
> git-status --diff
>
> shows diffs of modified files in the working tree.
>
> This makes it more clear what each diff means.
I'd rather say
git-commit --diff
or
git-diff --commit
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-06 10:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4574AC9E.3040506@gmail.com>
[not found] ` <4574BF70.8070100@lilypond.org>
2006-12-06 0:41 ` git newbie problems Graham Percival
2006-12-06 1:23 ` Jakub Narebski
2006-12-06 9:39 ` Han-Wen Nienhuys
2006-12-06 10:17 ` Jakub Narebski
2006-12-06 10:21 ` Han-Wen Nienhuys
2006-12-06 10:42 ` Johannes Schindelin
2006-12-06 1:35 ` Junio C Hamano
2006-12-06 22:19 ` Daniel Barkalow
2006-12-06 1:52 ` Tom Prince
[not found] ` <el5608$952$2@sea.gmane.org>
2006-12-06 8:01 ` Graham Percival
[not found] ` <45760545.2010801@gmail.com>
[not found] ` <Pine.LNX.4.63.0612060053400.28348@wbgn013.biozentrum.uni-wuerzburg.de>
[not found] ` <45761451.8020006@gmail.com>
[not found] ` <Pine.LNX.4.63.0612060157020.28348@wbgn013.biozentrum.uni-wuerzburg.de>
2006-12-06 9:55 ` git patch Han-Wen Nienhuys
2006-12-06 10:00 ` Junio C Hamano
2006-12-06 10:22 ` Jakub Narebski [this message]
[not found] ` <Pine.LNX.4.63.0612061105220.28348@wbgn013.biozentrum.uni-wuerzburg.de>
[not found] ` <457698E0.80207@lilypond.org>
[not found] ` <Pine.LNX.4.63.0612061147540.28348@wbgn013.biozentrum.uni-wuerzburg.de>
2006-12-06 11:27 ` Han-Wen Nienhuys
[not found] ` <20061206.105251.144349770.wl@gnu.org>
2006-12-06 12:27 ` [PATCH] cvs-migration document: make the need for "push" more obvious Johannes Schindelin
2006-12-06 12:32 ` Jakub Narebski
2006-12-06 13:14 ` Johannes Schindelin
2006-12-06 13:27 ` Jakub Narebski
2006-12-06 13:32 ` New users, was " Johannes Schindelin
2006-12-06 14:52 ` J. Bruce Fields
2006-12-06 14:52 ` Han-Wen Nienhuys
2006-12-06 14:58 ` J. Bruce Fields
2006-12-06 15:05 ` Han-Wen Nienhuys
2006-12-06 15:16 ` Johannes Schindelin
2006-12-06 17:19 ` J. Bruce Fields
2006-12-06 17:24 ` J. Bruce Fields
2006-12-06 17:44 ` Junio C Hamano
2006-12-07 4:18 ` [PATCH] Documentation: reorganize cvs-migration.txt J. Bruce Fields
2006-12-07 5:51 ` Junio C Hamano
2006-12-07 15:21 ` J. Bruce Fields
2006-12-07 14:28 ` Johannes Schindelin
2006-12-07 17:43 ` J. Bruce Fields
2006-12-07 17:50 ` Johannes Schindelin
2006-12-08 3:34 ` J. Bruce Fields
2006-12-08 7:25 ` Junio C Hamano
2006-12-09 3:58 ` J. Bruce Fields
2006-12-06 21:02 ` [PATCH] cvs-migration document: make the need for "push" more obvious Graham Percival
2006-12-06 21:45 ` J. Bruce Fields
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='el65h9$tfj$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=lilypond-devel@gnu.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).