git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: Junio C Hamano <gitster@pobox.com>, Petr Baudis <pasky@suse.cz>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Luben Tuikov <ltuikov@yahoo.com>,
	git@vger.kernel.org, jnareb@gmail.com
Subject: Re: [ANNOUNCE] git/gitweb.git repository
Date: Fri, 31 Aug 2007 19:15:23 -0700 (PDT)	[thread overview]
Message-ID: <400762.26134.qm@web31810.mail.mud.yahoo.com> (raw)
In-Reply-To: <7v4pifw45n.fsf@gitster.siamese.dyndns.org>

--- Junio C Hamano <gitster@pobox.com> wrote:
> Petr Baudis <pasky@suse.cz> writes:
> 
> > On Sat, Sep 01, 2007 at 03:25:16AM CEST, Johannes Schindelin wrote:
> >> On Fri, 31 Aug 2007, Luben Tuikov wrote:
> >> 
> >> > So what's the review process now?
> >> 
> >> Umm.  Pasky set it up, so it's Pasky who decides what goes in and what 
> >> not.  What exactly is your problem?
> >
> >   Junio will pull from it, so he has full right to ask. :-)
> 
> Well, I won't blindly pull from it, but honestly when it comes
> to gitweb I trust Pasky's judgement as much as I trust myself,
> if not even more.  And I think the review process Pasky
> described is good --- people will see both the patches on the
> list and code in action at repo.or.cz/.
> 
> I am a bit worried about the 'master' being a "StGIT stack",
> though.  Playgrounds to be cherry-picked from (aka 'pu') would
> make *perfect* sense to be managed that way (and the topics that
> go only 'pu' of git.git itself are managed the same except that
> I do not do so using StGIT), but I think we need a stable
> history for the branch git.git will eventually pull from.

That was my concern too, but seeing the immediate hostility
I got about asking about the review process I decided not
to mention it.

I'd be interesting to see how gitweb support pans out
given this initial hostility to inquiry of accountability.

Over the years I've seen that the best support and accountability
has been had when the maintainer is not the main contributor/developer,
especially for shared development. Otherwise personal preferences over
feature X and Y come into play and then things get ugly.  This is
why you were such a good maintainer of gitweb.

   Luben

  reply	other threads:[~2007-09-01  2:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31  0:01 [ANNOUNCE] git/gitweb.git repository Petr Baudis
2007-08-31  0:56 ` David Symonds
2007-08-31  1:00   ` David Symonds
2007-09-01  5:46   ` David Symonds
2007-09-07  6:39     ` David Symonds
2007-09-01  1:06 ` Luben Tuikov
2007-09-01  1:16   ` Petr Baudis
2007-09-01  1:23     ` Luben Tuikov
2007-09-01  1:25   ` Johannes Schindelin
2007-09-01  1:31     ` Petr Baudis
2007-09-01  1:44       ` Junio C Hamano
2007-09-01  2:15         ` Luben Tuikov [this message]
2007-09-01  4:57           ` Junio C Hamano
2007-09-01  2:06     ` Luben Tuikov
2007-09-01 15:15 ` Jon Smirl
2007-09-01 17:54   ` Junio C Hamano
2007-09-01 17:54 ` Jakub Narebski
2007-09-04  5:42 ` Junio C Hamano
2007-09-04  5:47   ` Adam Roben
2007-09-04  5:50   ` Shawn O. Pearce
2007-09-04  8:19     ` Junio C Hamano
2007-09-04  5:58   ` Andreas Ericsson
2007-09-04  9:38     ` Petr Baudis
2007-09-04  7:56   ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=400762.26134.qm@web31810.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=pasky@suse.cz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).