From: Junio C Hamano <gitster@pobox.com>
To: Florian La Roche <laroche@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Change feeds from commit to commitdiff output.
Date: Thu, 10 Jan 2008 12:21:21 -0800 [thread overview]
Message-ID: <7vtzll5t4u.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080110130900.GA9395@dudweiler.stuttgart.redhat.com> (Florian La Roche's message of "Thu, 10 Jan 2008 14:09:00 +0100")
Florian La Roche <laroche@redhat.com> writes:
> [PATCH] gitweb: Change feeds from commit to commitdiff output.
>
> Change feeds from displaying the commit to displaying the commitdiff
> output. This way the patches are shown directly and code review is
> done more easily via watching feeds.
>
> Signed-off-by: Florian La Roche <laroche@redhat.com>
I can see that easier access to commitdiff output is sometimes
desirable.
If you are making this change unconditional, however, I think
there needs a list discussion between you and the silent
majority of people that have been perfectly happy with the
current "log only" behaviour.
And to have that discussion, you first have to wake them up,
which this patch would serve well as a wake-up call. But if
that was the purpose of the posting, please (1) mark the patch
as such (commonly done by saying [RFC/PATCH] instead), and (2)
keep me out of the "To:" list, if the patch is not for inclusion
but for discussion ("cc:" is fine but it's redundant as long as
you are sending to the list).
After such a discussion, we may end up finding out that
everybody have been silently unhappy and wanted to have
commitdiff there, and agree on doing this unconditionally.
But we do not know that yet.
Thanks.
next prev parent reply other threads:[~2008-01-10 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 13:09 [PATCH] gitweb: Change feeds from commit to commitdiff output Florian La Roche
2008-01-10 20:21 ` Junio C Hamano [this message]
2008-01-11 6:53 ` Florian La Roche
2008-01-11 11:12 ` Jakub Narebski
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=7vtzll5t4u.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=laroche@redhat.com \
/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).