git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Clifford Caoile" <piyo@users.sourceforge.net>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: [PATCH] Docs gitk: Explicitly mention -d, --date-order option
Date: Sat, 12 Apr 2008 18:49:13 +0900	[thread overview]
Message-ID: <1f748ec60804120249u8d790e0t814f2c675fc4a464@mail.gmail.com> (raw)

gitk can show the commits in --date-order which is commits sorted by
Committer Date. -d is a gitk feature, which in turn converts to
--date-order, which is a git-log feature. It is useful to mention.

git-branch, a Javascript based git repo viewer, displays in
--date-order.

Signed-off-by: Clifford Caoile <piyo@users.sourceforge.net>
---
 Documentation/gitk.txt |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/Documentation/gitk.txt b/Documentation/gitk.txt
index 29edafc..d247d63 100644
--- a/Documentation/gitk.txt
+++ b/Documentation/gitk.txt
@@ -41,6 +41,12 @@ frequently used options.

 	Show all branches.

+-d, --date-order::
+
+	Shows commits by Committer Date order. Note that the date column is
+	Author Date, so it may appear to be out of order. If this option is
+	not set, gitk displays in --topo-order. See linkgit:git-log[1].
+
 <revs>::

 	Limit the revisions to show. This can be either a single revision
-- 
1.5.4.2.1161.g1a6f0

             reply	other threads:[~2008-04-12  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12  9:49 Clifford Caoile [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-18 13:16 [PATCH] Docs gitk: Explicitly mention -d, --date-order option Clifford Caoile
2008-04-19  6:58 ` Junio C Hamano
2008-04-19  7:28   ` Raimund Bauer
2008-04-19  7:35   ` Clifford Caoile
2011-04-01  8:05   ` Robert Pollak

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=1f748ec60804120249u8d790e0t814f2c675fc4a464@mail.gmail.com \
    --to=piyo@users.sourceforge.net \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).