git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Luben Tuikov <ltuikov@yahoo.com>, git@vger.kernel.org, jnareb@gmail.com
Subject: Re: [ANNOUNCE] git/gitweb.git repository
Date: Sat, 1 Sep 2007 03:31:59 +0200	[thread overview]
Message-ID: <20070901013159.GP1219@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0709010224410.28586@racer.site>

  Hi,

On Sat, Sep 01, 2007 at 03:25:16AM CEST, Johannes Schindelin wrote:
> On Fri, 31 Aug 2007, Luben Tuikov wrote:
> 
> > --- Petr Baudis <pasky@suse.cz> wrote:
> > >   Hi,
> > > 
> > >   due to popular (Junio's) demand, I have set up a gitweb-oriented fork
> > > of git at repo.or.cz:
> > > 
> > > 	http://repo.or.cz/w/git/gitweb.git
> > > 
> > >   It is meant as a hub for various gitweb-related patches and
> > > development efforts. So far it is pre-seeded by the patches repo.or.cz's
> > > gitweb uses.
> > 
> > Is this right?
> > 
> > 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. :-) As I wrote
in the web README, to enter #next your patch should see some git@ review;
that holds for repo.or.cz patches as well as for any other patches. I
suppose we will sort out the exact distinction between #next and #master
on the fly; the general idea is that patches that go on #master have
more or less approached perfectness. ;-)

-- 
				Petr "Pasky" Baudis
Early to rise and early to bed makes a male healthy and wealthy and dead.
                -- James Thurber

  reply	other threads:[~2007-09-01  1:32 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 [this message]
2007-09-01  1:44       ` Junio C Hamano
2007-09-01  2:15         ` Luben Tuikov
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=20070901013159.GP1219@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=ltuikov@yahoo.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.
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).