From mboxrd@z Thu Jan 1 00:00:00 1970 From: layer Subject: the workflow (from your POV) of managing git Date: Sun, 31 Jan 2010 21:00:41 -0800 Message-ID: <20375.1265000441@relay.known.net> To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Mon Feb 01 06:00:47 2010 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NboP0-0007fD-Q6 for gcvg-git-2@lo.gmane.org; Mon, 01 Feb 2010 06:00:47 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750724Ab0BAFAm (ORCPT ); Mon, 1 Feb 2010 00:00:42 -0500 Received: from relay.known.net ([173.13.135.57]:42286 "EHLO relay.known.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750704Ab0BAFAl (ORCPT ); Mon, 1 Feb 2010 00:00:41 -0500 Received: from localhost (127.0.0.1) by relay.known.net (Allegro Maild v1.2.21) id 000000078885; Sun, 31 Jan 2010 21:00:41 -0800 X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.1.1 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Junio, greetings. Have you written anything up that tells people how you manage the git project? Something that could be used by other project leaders? I've been googling and haven't been able to find anything other than documents which describe the process from the other side (people submitting patches). A lot can be gleaned by looking at it from the patch-submitter side, but I'm guessing there are lots of little tips that project leads could learn from by seeing a document on the process you use. For example, do you have a script that generates the "what's cooking in..." emails? Thanks! Kevin