From: Petr Baudis <pasky@suse.cz>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: [RFCv3 1/2] gitweb: add patch view
Date: Sat, 6 Dec 2008 14:10:58 +0100 [thread overview]
Message-ID: <20081206131058.GB10491@machine.or.cz> (raw)
In-Reply-To: <cb7bb73a0812060501s6a3faea7l74e81c2a591ba2a7@mail.gmail.com>
On Sat, Dec 06, 2008 at 02:01:09PM +0100, Giuseppe Bilotta wrote:
> On Sat, Dec 6, 2008 at 1:46 AM, Junio C Hamano <gitster@pobox.com> wrote:
> > Some things, like sitewide default css changes, cannot be made disabled
> > by default. But a new feature can easily be kept disabled by default not
> > to cause needless surprises.
>
> In the eternal war between making feature easily available and not
> disturbing the user too much between upgrades, I'm more on the 'making
> available' field, especially when the features are not particularly
> invasive (e.g., the patch view only adds one single link, on the
> navigation bar, and only in some views).
>
> It should also be noted that if the sysadmin deploys a new software
> version without telling its users, there's an obvious communication
> problem between the sysadmin and its users, but that's not something
> the tool developers should try to work around. Otherwise we'd still be
> offering the dash version of the commands by default.
I feel exactly the same.
Acked-by: Petr Baudis <pasky@suse.cz>
Same goes for the patches, I haven't had time to examine them in detail
but the general shape looks fine.
next prev parent reply other threads:[~2008-12-06 13:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 22:59 [RFCv3 0/2] gitweb: patch view Giuseppe Bilotta
2008-12-03 22:59 ` [RFCv3 1/2] gitweb: add " Giuseppe Bilotta
2008-12-03 22:59 ` [RFCv3 2/2] gitweb: links to patch action in commitdiff and shortlog view Giuseppe Bilotta
2008-12-06 0:53 ` Jakub Narebski
2008-12-06 13:25 ` Giuseppe Bilotta
2008-12-06 15:25 ` Jakub Narebski
2008-12-03 23:55 ` [RFCv3 1/2] gitweb: add patch view Junio C Hamano
2008-12-04 0:20 ` Giuseppe Bilotta
2008-12-04 0:40 ` Junio C Hamano
2008-12-04 1:48 ` Jakub Narebski
2008-12-04 7:24 ` Giuseppe Bilotta
2008-12-06 0:34 ` Jakub Narebski
2008-12-06 0:46 ` Junio C Hamano
2008-12-06 1:09 ` Jakub Narebski
2008-12-06 1:26 ` Junio C Hamano
2008-12-06 13:01 ` Giuseppe Bilotta
2008-12-06 13:10 ` Petr Baudis [this message]
2008-12-06 12:34 ` Giuseppe Bilotta
2008-12-06 13:09 ` Jakub Narebski
2008-12-06 13:46 ` Giuseppe Bilotta
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=20081206131058.GB10491@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
--cc=jnareb@gmail.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).