git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon <turner25@gmail.com>
To: Eric Raymond <esr@snark.thyrsus.com>
Cc: git@vger.kernel.org
Subject: Re: More git status --porcelain lossage
Date: Sat, 10 Apr 2010 14:48:05 -0400	[thread overview]
Message-ID: <l2k5f14cf5e1004101148h5cf8dc4bm1836cf1c5fc8abfb@mail.gmail.com> (raw)
In-Reply-To: <20100409190601.47B37475FEF@snark.thyrsus.com>

> A format properly designed for script parseability should use even use
> whitespace as a field separator.
>
> Why?
>
> Because if you do that, front ends *will* do field analysis using a
> naive split-on-whitespace operation.  And then...someday...someone
> will try to run one of these of these on a volume from a system where
> filenames contain embedded whitespace.  Like Mac OS X or Windows.

Why not use an XML output?
Plain text is easier to parse, but XML may give this extra durability
you are looking for?

Simon

  parent reply	other threads:[~2010-04-10 18:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 19:06 More git status --porcelain lossage Eric Raymond
2010-04-09 19:09 ` Eric Raymond
2010-04-09 19:22 ` Jakub Narebski
2010-04-09 19:50   ` Eric Raymond
2010-04-10  4:12 ` Jeff King
2010-04-10  4:14   ` Jeff King
2010-04-10 18:48 ` Simon [this message]
2010-04-10 19:01   ` Jakub Narebski
2010-04-10 19:41     ` Eric Raymond
2010-04-10 20:31       ` Martin Langhoff
2010-04-10 22:28         ` Paolo Bonzini
2010-04-10 23:06           ` Eric Raymond
2010-04-11 11:04           ` David Aguilar
2010-04-10 21:21       ` Jakub Narebski
2010-04-10 22:57         ` Eric Raymond
2010-04-10 19:30   ` Eric Raymond
2010-04-10 19:39     ` Ævar Arnfjörð Bjarmason
2010-04-10 21:24       ` Simon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=l2k5f14cf5e1004101148h5cf8dc4bm1836cf1c5fc8abfb@mail.gmail.com \
    --to=turner25@gmail.com \
    --cc=esr@snark.thyrsus.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).