From: Dan Holmsand <holmsand@gmail.com>
To: git@vger.kernel.org
Cc: Petr Baudis <pasky@ucw.cz>
Subject: Re: [PATCH] Many new features for cg-diff and cg-log
Date: Wed, 08 Jun 2005 23:03:24 +0200 [thread overview]
Message-ID: <42A75D1C.1060102@gmail.com> (raw)
In-Reply-To: <20050608204012.GN982@pasky.ji.cz>
Petr Baudis wrote:
> Dear diary, on Wed, Jun 08, 2005 at 10:28:05PM CEST, I got a letter
> where Dan Holmsand <holmsand@gmail.com> told me that...
>>Sorry about the monster patch, but I wanted to get it to you quickly...
>
>
> Well, it can always go to 0.11.3 or something. I probably wouldn't take
> it to the tree just before release anyway even if you sent it split up,
> since due to the size of the changes, it's bound to have some hidden
> bugs. ;-)
Nah... Seriously, that's a wise decision. I just saw that you we're
working on cg-log, and wanted to save you some potential doublework by
sending what I've got in a hurry.
I have, however, been using this myself for quite some time, so it's
reasonably well tested.
>>[PATCH] Many new features for cg-diff and cg-log
>
>
> Ok, this is really too big. Could you please split it up some? Also,
> I've been hacking on cg-log too (and will make it use git-diff-tree -v
> yet this evening), so you'll need to update it to apply to the latest
> version.
Sure. I'll try to split it up, somewhat (but the changes *are* pretty
inter-related...).
>
> I like what's inside (at least from the description), though! (Well,
> mostly. But I'll comment on specific patches. No major objections.)
>
>
>>- Selection of ranges by date or maximum number of commits to show.
>
>
> Ad date, isn't that already supported now? The -r arguments can be a
> date. Ad maximum number of commits, what'd be its use?
>
The new date thing doesn't work very well for cg-log: it's hardcoded to
HEAD. That means that attempts to do, say, "cg-log -rorigin:-1day" will
not at all do what you want. Not to mention "cg-log -m -r-1day". And I
think it's a little clearer to separate the two: "cg-log -rorigin
--max-age=-1day" (there's a short option too).
Max number of commits is perhaps not all that useful, unless you want to
save cg-log output to file, for example. But it's easy to do :-)
Oh, and I forgot to mention the "pickaxe" support. "cg-log -S foobar"
uses git-diff-tree -S to "search in diffs". Really very, very useful.
/dan
prev parent reply other threads:[~2005-06-08 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 13:46 cogito-0.10 broken for cg-commit < logmessagefile Russell King
2005-06-08 16:28 ` Catalin Marinas
2005-06-08 18:17 ` Petr Baudis
2005-06-08 20:28 ` [PATCH] Many new features for cg-diff and cg-log Dan Holmsand
2005-06-08 20:40 ` Petr Baudis
2005-06-08 21:03 ` Petr Baudis
2005-06-08 21:03 ` Dan Holmsand [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=42A75D1C.1060102@gmail.com \
--to=holmsand@gmail.com \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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).