From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6841 invoked by alias); 10 Aug 2015 14:02:56 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 36066 Received: (qmail 17371 invoked from network); 10 Aug 2015 14:02:53 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS autolearn=ham autolearn_force=no version=3.4.0 X-AuditID: cbfec7f4-f79c56d0000012ee-7d-55c8acaf2c0b Date: Mon, 10 Aug 2015 14:52:12 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: [PATCH 00/18] Updates for _tmux Message-id: <20150810145212.6aedd398@pwslap01u.europe.root.pri> In-reply-to: <1439213258-14196-1-git-send-email-ft@bewatermyfriend.org> References: <1439213258-14196-1-git-send-email-ft@bewatermyfriend.org> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsVy+t/xa7rr15wINdh2TMXiYPNDJgdGj1UH PzAFMEZx2aSk5mSWpRbp2yVwZXy/upmpoIelYu/fI4wNjHOZuxg5OSQETCQWH9rCCGGLSVy4 t56ti5GLQ0hgKaNE+6lj7BDODCaJtv+LoZxtjBL3/p8Da2cRUJV4MfkwK4jNJmAoMXXTbLBR IgLiEmfXnmcBsYUFdCTuX/3DBmLzCthLNH96zgRicwq4S6x++gGsRkjATaJz11qwOL+AvsTV v5+YIE6yl5h55QwjRK+gxI/J98DqmQW0JDZva2KFsOUlNq95ywwxR13ixt3d7BMYhWYhaZmF pGUWkpYFjMyrGEVTS5MLipPScw31ihNzi0vz0vWS83M3MULC9ssOxsXHrA4xCnAwKvHwzth8 PFSINbGsuDL3EKMEB7OSCG/KqhOhQrwpiZVVqUX58UWlOanFhxilOViUxHnn7nofIiSQnliS mp2aWpBaBJNl4uCUamD0+fo849PUBpnOJi+d6si3otPSV4T4X5kS93+zxq8lr2ftfvbMNrFo Rv0Xn8Nlc67PY7/Nu6j1J+O1q5J7+V4ZMeQ8OiVdtbly26Wli59I6K4tsSlqvq45J+/VSiXz N1uWTuOe37M+eeWKve8yWv9o36yukbu5J/TqxQDj17+07W95Ca7k23hDSImlOCPRUIu5qDgR AJ4/5P5XAgAA On Mon, 10 Aug 2015 15:27:20 +0200 Frank Terbeck wrote: > Since this is a fairly large update: Should I wait until 5.0.9 is out or do I > go ahead and commit it right away? Bear in mind that the completion was quite > out of date, but also that this is a rather large update... So I don't know. My general philosophy of this is that it's disconnected from the core code well enough that it's not really much of a risk putting it in, so if you fell it's basically working, go ahead. pws