git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian La Roche <laroche@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Change feeds from commit to commitdiff output.
Date: Fri, 11 Jan 2008 07:53:48 +0100	[thread overview]
Message-ID: <20080111065348.GA3967@dudweiler.stuttgart.redhat.com> (raw)
In-Reply-To: <7vtzll5t4u.fsf@gitster.siamese.dyndns.org>

On Thu, Jan 10, 2008 at 12:21:21PM -0800, Junio C Hamano wrote:
> 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.


Hello Junio,

Right, this is a change in behaviour. Maybe a config option
for this would be good, so that users can configure their
wanted output style.


> 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).


Ok.


> 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.


>From asking people, most don't use feeds to follow development
checkins, but prefer to keep with mailinglists and looking only
at the repos for their own interesting parts.

Hope more people will speak up here on the git@ list.

Thanks a lot,

Florian La Roche

  reply	other threads:[~2008-01-11  6:54 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
2008-01-11  6:53   ` Florian La Roche [this message]
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=20080111065348.GA3967@dudweiler.stuttgart.redhat.com \
    --to=laroche@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).