From: Jonas Fonseca <fonseca@diku.dk>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
Git Mailing List <git@vger.kernel.org>,
Timo Hirvonen <tihirvon@gmail.com>
Subject: Re: [PATCH] git-rev-list(1): group options; reformat; document more options
Date: Fri, 1 Sep 2006 22:33:48 +0200 [thread overview]
Message-ID: <20060901203348.GA27515@diku.dk> (raw)
In-Reply-To: <7vsljc78m9.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote Thu, Aug 31, 2006:
> Linus Torvalds <torvalds@osdl.org> writes:
>
> > On Fri, 1 Sep 2006, Jonas Fonseca wrote:
> >
> >> [The "-r" and "-t" option] do not seem to make sense for
> >> git-rev-list, however if you pass either to git-log, the output
> >> seems to make room for a diff, adding one extra newline, but
> >> without appending any diff.
> >
> > Ahh. I think that a "-r" without any other request for patches (or
> > "--name-status" or similar) should probably imply "--raw". At least
> > that was how it historically worked..
:set paste
commit 17985627455901b6ae3a471b67d46239463cebb5
Author: Timo Hirvonen <tihirvon@gmail.com>
Date: Tue Jun 27 16:27:51 2006 +0300
log --raw: Don't descend into subdirectories by default
Only do so when -r is given.
> > Anyway, _if_ it ever worked (and I think it did, but I'm way too lazy to
> > bother checking), this may have been broken by the extensive diff option
> > cleanups by Timo in June. Timo? Junio?
>
> I think it did too. I am kind of surprised that nobody noticed
> and t4013 test (which was done specifically to catch potential
> behaviour change by Timo's patch) did not check for this
> particular case.
commit 0e677e1a6b0d1c0e848ed19d18dda1c3c797c75e
Author: Timo Hirvonen <tihirvon@gmail.com>
Date: Sat Jun 24 20:25:08 2006 +0300
DIFF_FORMAT_RAW is not default anymore
diff_setup() used to initialize output_format to DIFF_FORMAT_RAW. Now
the default is 0 (no output) so don't compare against DIFF_FORMAT_RAW to
see if any diff format command line flags were given.
:set nopaste
So they are working as intended. I'll look into updating the patch.
BTW, --author=timo made this very easy. ;)
--
Jonas Fonseca
--
VGER BF report: U 0.5
prev parent reply other threads:[~2006-09-01 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 22:37 [PATCH] git-rev-list(1): group options; reformat; document more options Jonas Fonseca
2006-08-31 23:02 ` Linus Torvalds
2006-08-31 23:08 ` Jonas Fonseca
2006-08-31 23:15 ` Linus Torvalds
2006-09-01 0:06 ` Junio C Hamano
2006-09-01 20:33 ` Jonas Fonseca [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=20060901203348.GA27515@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tihirvon@gmail.com \
--cc=torvalds@osdl.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.