Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Jon Beniston <jon@beniston.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Patch to support spaces in filenames & paths
Date: Tue, 02 Dec 2008 21:20:00 -0000	[thread overview]
Message-ID: <4935A5E2.5050503@vmware.com> (raw)
In-Reply-To: <7D653316E38B4305941199D722BF20B0@bibi>

Jon Beniston wrote:
> Hi,
> 
> Attached is a patch that adds support for spaces in filenames or paths for
> CLI commands such as restore, by supporting quotes. E.g:
> 
> restore "path with spaces/test.x" 
> 
> 2008-12-02 Jon Beniston <jon@beniston.com>
> 
>         * cli/cli-dump.c: (scan_filename_with_cleanup) Add support for
> quoted 
>         strings to allow spaces in paths and filenames.
> 

Fascinating -- now we have two overlapping patches submitted on
the same day, both mentioning "restore" as one of the commands
affected.

Denis, is it possible that Jon's patch will serve in place of
the filename portion of your patch?  And that you could then
resubmit your patch with just the other portions?

Jon's patch:
http://sourceware.org/ml/gdb-patches/2008-12/msg00032.html

Denis' patch:
http://sourceware.org/ml/gdb-patches/2008-12/msg00029.html




  reply	other threads:[~2008-12-02 21:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 13:09 Jon Beniston
2008-12-02 21:20 ` Michael Snyder [this message]
2008-12-02 23:38   ` Daniel Jacobowitz
2008-12-03  0:04     ` Pedro Alves
2008-12-03  0:26     ` Doug Evans
2008-12-04  9:38       ` Denis PILAT
2008-12-04 13:11         ` Daniel Jacobowitz
2008-12-10 15:32           ` Denis PILAT
2008-12-10 16:20             ` Daniel Jacobowitz
2009-01-05 14:20               ` Denis PILAT

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=4935A5E2.5050503@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jon@beniston.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