From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: [PATCH v3] tag: support --sort= Date: Wed, 26 Feb 2014 06:17:11 -0500 Message-ID: <20140226111711.GA3122@sigill.intra.peff.net> References: <1393039762-4843-1-git-send-email-pclouds@gmail.com> <1393330935-22229-1-git-send-email-pclouds@gmail.com> <20140226090511.GA32537@sigill.intra.peff.net> <20140226110803.GG25711@sigill.intra.peff.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Git Mailing List , Junio C Hamano To: Duy Nguyen X-From: git-owner@vger.kernel.org Wed Feb 26 12:17:24 2014 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WIcUH-000228-Up for gcvg-git-2@plane.gmane.org; Wed, 26 Feb 2014 12:17:18 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751344AbaBZLRN (ORCPT ); Wed, 26 Feb 2014 06:17:13 -0500 Received: from cloud.peff.net ([50.56.180.127]:57295 "HELO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751100AbaBZLRN (ORCPT ); Wed, 26 Feb 2014 06:17:13 -0500 Received: (qmail 11869 invoked by uid 102); 26 Feb 2014 11:17:13 -0000 Received: from c-71-63-4-13.hsd1.va.comcast.net (HELO sigill.intra.peff.net) (71.63.4.13) (smtp-auth username relayok, mechanism cram-md5) by peff.net (qpsmtpd/0.84) with ESMTPA; Wed, 26 Feb 2014 05:17:13 -0600 Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Wed, 26 Feb 2014 06:17:11 -0500 Content-Disposition: inline In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Wed, Feb 26, 2014 at 06:11:54PM +0700, Duy Nguyen wrote: > On Wed, Feb 26, 2014 at 6:08 PM, Jeff King wrote: > > I'd worry slightly, though, that there are other schemes where that > > behaves poorly. Should we optimize for git's version numbering, or for > > what most other projects want? There could even be room for two types of > > version-compare. But before thinking about that, I'd want to know why > > glibc behaves as it does. > > We don't have to force one version style for all projects. We could > provide --sort="thisver:refname" vs. "thatver:refname", or put the > "-pre" part in config file. The important thing is we can control the > version algorithm. Right, exactly. It may make sense to just do it the way _we_ think is sensible for now, then, and we can add a glibc-compatible one later if somebody actually wants it. -Peff