git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: Filename quoting / parsing problem
Date: Wed, 6 Jan 2010 01:04:25 +0100	[thread overview]
Message-ID: <201001060104.25737.agruen@suse.de> (raw)
In-Reply-To: <201001022148.47841.agruen@suse.de>

On Saturday 02 January 2010 09:48:47 pm Andreas Gruenbacher wrote:
> On Saturday 02 January 2010 07:37:08 pm Junio C Hamano wrote:
> > I don't think it happened in the GNU land yet, and you would be the
> > person to know about it ;-).
> 
> I'm working on it ...

The "experimental" branch [*] now has very lightly tested code for parsing 
most extended headers ("index", "rename from", "rename to", "copy from", "copy 
to", "old mode", "new mode", "deleted file mode", "new file mode").  Most 
things should work, except:

 * Doesn't parse filenames in "diff --git" lines.  (I tried to argue why
   those lines are a problem in this thread.)

 * sha1 checksums are not verified right now.  I'm not sure when that should
   happen: always by default, or only optionally?  (Like verifying file modes,
   this is going to surprise a lot of users.)

 * Similarity and dissimilarity headers are ignored.

 * Binary diffs are no supported.  I think GNU patch should recognize them and
   give a reasonable message for now.


[*] http://git.savannah.gnu.org/cgit/patch.git/log/?h=experimental


Can you guys please do something to make parsing of filenames in "diff --git" 
lines a lot easier, or unnecessary?

Thanks!
Andreas

  reply	other threads:[~2010-01-06  0:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-01 17:44 Filename quoting / parsing problem Andreas Gruenbacher
2010-01-01 19:50 ` Junio C Hamano
2010-01-01 20:01   ` Junio C Hamano
2010-01-02 11:36     ` Andreas Gruenbacher
2010-01-02 18:37       ` Junio C Hamano
2010-01-02 20:48         ` Andreas Gruenbacher
2010-01-06  0:04           ` Andreas Gruenbacher [this message]
2010-01-06  1:32             ` Junio C Hamano
2010-01-06  1:08           ` Junio C Hamano
2010-01-06 10:06             ` Andreas Schwab

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=201001060104.25737.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).