From: Luben Tuikov <ltuikov@yahoo.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Enable tree (directory) history display
Date: Fri, 30 Jun 2006 20:10:04 -0700 (PDT) [thread overview]
Message-ID: <20060701031004.29384.qmail@web31801.mail.mud.yahoo.com> (raw)
In-Reply-To: <7v3bdmf2p6.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
> Luben Tuikov <ltuikov@yahoo.com> writes:
>
> > I took a comparative look with and without "--full-history",
> > and FWIW, enabling full history just clobbers the output with a lot
> > of unnecessary information. I.e. it shows merges which do not have
> > direct consequence or change to the files in the path spec specified
> > after the "--".
> >...
> > FWIW, I think that the original intention (had there been a choice)
> > would've been to show only most relevant history, i.e. changes
> > directly related to paths and files after the "--".
>
> Sounds sane. Maybe we should clearly explain this behaviour
> change in the commit log and claim it as an improvement. We
> might even want to do --no-merges if we go that route.
I agree. Indeed, this would definitely be an improvement.
Luben
next prev parent reply other threads:[~2006-07-01 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 1:00 [PATCH] Enable tree (directory) history display Luben Tuikov
2006-07-01 2:10 ` Junio C Hamano
2006-07-01 2:43 ` Luben Tuikov
2006-07-01 3:01 ` Junio C Hamano
2006-07-01 3:10 ` Luben Tuikov [this message]
2006-07-01 3:21 ` Linus Torvalds
2006-07-01 3:45 ` Linus Torvalds
2006-07-01 22:45 ` Luben Tuikov
2006-07-01 19:38 ` Luben Tuikov
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=20060701031004.29384.qmail@web31801.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox