From: Anders Lindgren <andlind@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21984@debbugs.gnu.org
Subject: bug#21984: 25.0.50; Creating a new file in a new directory in a subversion sandbox fails
Date: Fri, 11 Dec 2015 12:05:16 +0100 [thread overview]
Message-ID: <CABr8ebZ32zqgU9_nB76p08hpB7S0HVdsEDfhZNv-=4h=hEzcGw@mail.gmail.com> (raw)
In-Reply-To: <83a8ph8d9x.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
From my point of view, you can close it.
In fact, I sent a mail to the bug server this morning to close it, but it
doesn't seem to have been registered.
-- Anders
On Fri, Dec 11, 2015 at 11:56 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Fri, 11 Dec 2015 11:13:27 +0100
> > From: Anders Lindgren <andlind@gmail.com>
> > Cc: 21984@debbugs.gnu.org
> >
> > Does the patch below solve the problem?
> >
> > Yes, it does. And it's a better solution than mine.
>
> Thanks, pushed.
>
> > About the code. Why does it use `cd' -- I thought it mainly was for
> interactive
> > use. However, I didn't want to change the code more than necessary.
>
> I don't know why it uses 'cd'. Presumably, something related to how
> SVN works, but I'm no expert.
>
> Should we close this bug, or is there anything else left?
>
[-- Attachment #2: Type: text/html, Size: 1445 bytes --]
next prev parent reply other threads:[~2015-12-11 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 18:40 bug#21984: 25.0.50; Creating a new file in a new directory in a subversion sandbox fails Anders Lindgren
2015-11-22 18:59 ` Eli Zaretskii
2015-11-22 19:07 ` Anders Lindgren
[not found] ` <83si398l0w.fsf@gnu.org>
2015-12-11 10:13 ` Anders Lindgren
[not found] ` <83a8ph8d9x.fsf@gnu.org>
2015-12-11 11:05 ` Anders Lindgren [this message]
[not found] ` <834mfp8cp3.fsf@gnu.org>
2015-12-11 11:30 ` Anders Lindgren
2015-12-11 19:06 ` Glenn Morris
2015-12-11 19:29 ` Anders Lindgren
2015-12-11 6:22 ` bug#21984: Fixed subversion vc problem Anders Lindgren
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='CABr8ebZ32zqgU9_nB76p08hpB7S0HVdsEDfhZNv-=4h=hEzcGw@mail.gmail.com' \
--to=andlind@gmail.com \
--cc=21984@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.