From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Pitre Subject: Re: Planning for 1.7.5 and 1.8.0 Date: Mon, 31 Jan 2011 23:16:13 -0500 (EST) Message-ID: References: <7vzkqh8vqw.fsf@alter.siamese.dyndns.org> <7vwrll57ha.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Boundary_(ID_hi31PrzXm+FF9X6wh17FHQ)" Cc: git@vger.kernel.org To: Nguyen Thai Ngoc Duy X-From: git-owner@vger.kernel.org Tue Feb 01 05:16:20 2011 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 1Pk7f9-0000LM-G0 for gcvg-git-2@lo.gmane.org; Tue, 01 Feb 2011 05:16:19 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754293Ab1BAEQO (ORCPT ); Mon, 31 Jan 2011 23:16:14 -0500 Received: from relais.videotron.ca ([24.201.245.36]:49651 "EHLO relais.videotron.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752520Ab1BAEQO (ORCPT ); Mon, 31 Jan 2011 23:16:14 -0500 Received: from xanadu.home ([66.130.28.92]) by vl-mh-mrz25.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTP id <0LFX00JF37TEVUA0@vl-mh-mrz25.ip.videotron.ca> for git@vger.kernel.org; Mon, 31 Jan 2011 23:15:14 -0500 (EST) X-X-Sender: nico@xanadu.home In-reply-to: User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --Boundary_(ID_hi31PrzXm+FF9X6wh17FHQ) Content-type: TEXT/PLAIN; charset=UTF-8 Content-transfer-encoding: 8BIT On Tue, 1 Feb 2011, Nguyen Thai Ngoc Duy wrote: > On Tue, Feb 1, 2011 at 12:05 AM, Junio C Hamano wrote: > > Now the 1.7.4 release is out, I'd like people to help thinking about the > > next cycle(s). > > > > As a discussion-starter, here are my random wishes.  Even though this does > > not attempt to be exhaustive, keeping the number of goals manageably small > > may help us focus. > > Another random wish, which does not come with a proposal. How about > tag namespace (ie. tags from a remote stay in remote namespace)? Please make this into a proper proposal. this would be indeed a huge improvement. Nicolas --Boundary_(ID_hi31PrzXm+FF9X6wh17FHQ)--