From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: [GSoC update] Sequencer for inclusion Date: Mon, 11 Jul 2011 18:14:19 -0400 Message-ID: <20110711221419.GE30155@sigill.intra.peff.net> References: <1310396048-24925-1-git-send-email-artagnon@gmail.com> <20110711171713.GA5963@elie> <7vpqlgbjmd.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Jonathan Nieder , Ramkumar Ramachandra , Git List , Christian Couder , Daniel Barkalow To: Junio C Hamano X-From: git-owner@vger.kernel.org Tue Jul 12 00:14:29 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 1QgOkF-0002Zx-3X for gcvg-git-2@lo.gmane.org; Tue, 12 Jul 2011 00:14:27 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757920Ab1GKWOW (ORCPT ); Mon, 11 Jul 2011 18:14:22 -0400 Received: from 99-108-226-0.lightspeed.iplsin.sbcglobal.net ([99.108.226.0]:35751 "EHLO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756169Ab1GKWOV (ORCPT ); Mon, 11 Jul 2011 18:14:21 -0400 Received: (qmail 5730 invoked by uid 107); 11 Jul 2011 22:14:45 -0000 Received: from sigill.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.7) (smtp-auth username relayok, mechanism cram-md5) by peff.net (qpsmtpd/0.84) with ESMTPA; Mon, 11 Jul 2011 18:14:45 -0400 Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Mon, 11 Jul 2011 18:14:19 -0400 Content-Disposition: inline In-Reply-To: <7vpqlgbjmd.fsf@alter.siamese.dyndns.org> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Mon, Jul 11, 2011 at 01:07:20PM -0700, Junio C Hamano wrote: > > To be precise, the format used includes > > > > strategy-option = patience | renormalize > > > > to represent the effect of "-Xpatience -Xrenormalize". My only worry > > about that is that the "|" can sound like "or", which would seem > > strange to a user that does not necessarily develop software (so is > > not thinking about bitfields). The format used in config files puts > > > > strategy-option = patience > > strategy-option = renormalize > > > > as separate lines. > > A very good point again. I do not think anywhere in our codebase we use > "|" as a separator for state files (either used for internal or exposed to > the end user), and we probably would want to be consistent across > commands. I had the same feeling about the "|". I'm a little confused about what these options are good for, though. Is it purely about saving some persistent data between runs, and nobody else is going to look at it? In that case, I don't think it matters what the format is. Use some unambiguous encoding that we already have available (like sq_quote_argv and sq_dequote_argv), and write as little code as possible. Or is it something that, like the information in .git/rebase-apply, people might want to read or tweak? In that case, might it make sense to follow that lead and split things into one file per item? That keeps the parsing burden extremely low for things like shell scripts (or shell users) who might want to read or tweak. -Peff