bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] maint: HACKING: mention a few more useful git commands


From: Jim Meyering
Subject: [PATCH] maint: HACKING: mention a few more useful git commands
Date: Sun, 17 May 2009 17:52:47 +0200

FYI,

>From 088a7ca9b155fde8d8af0c3754b7df3d45485591 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Sun, 17 May 2009 17:49:24 +0200
Subject: [PATCH] maint: HACKING: mention a few more useful git commands

* HACKING (Miscellaneous useful git commands): Add a few.
---
 HACKING |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/HACKING b/HACKING
index ad3e39f..ae43e3a 100644
--- a/HACKING
+++ b/HACKING
@@ -404,10 +404,16 @@ See the manpage for git-apply for details.
 Miscellaneous useful git commands
 =================================

-  * gitk: give a graphical view of the revision graph
+  * gitk: give a graphical view of the revision graph of the current branch
+  * gitk --all: same, but display all branches
   * git log: to get most of the same info in text form
   * git log -p: same as above, but with diffs
   * git log -p SOME_FILE: same as above, but limit to SOME_FILE
+  * git log -p -2 SOME_FILE: same as above, but print only two deltas
+  * git log -p -1: print the most recently committed change set
+  * git format-patch --stdout -1 > FILE: output the most recently committed
+      change set, in a format suitable to be submitted and/or applied via
+      "git am FILE".
   * git reset --soft HEAD^: Commit the delta required to restore
       state to the revision just before HEAD (i.e., next-to-last).
   * git rebase -i master: run this from on a branch, and it gives
--
1.6.3.1.135.g540c




reply via email to

[Prev in Thread] Current Thread [Next in Thread]