From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: emacs-repository-{version|branch} on Windows
Date: Fri, 4 Nov 2022 21:42:16 +0100 [thread overview]
Message-ID: <CAAeL0SR7c3HfuJ_b+=dXvsoAwRUNXH8aGpnzPCL8yxL=3oA5=Q@mail.gmail.com> (raw)
In-Reply-To: <83tu3e4g5n.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
On Fri, Nov 4, 2022 at 9:29 PM Eli Zaretskii <eliz@gnu.org> wrote:
> Is your ~/.emacs.d directory on the same drive as the system, i.e. on drive
C:\?
No. C: is the system drive, but I have all development tools (and most
other things) in D:
> Then taking ownership is easier, because there aren't any protected
directories,
> This is basic Windows system setup, nothing to do with Emacs per se.
I did so in the past. Then I had to replace that hard disk and couldn't
clone it, had to copy things. But that disk also contains the \User
directories, so it wasn't trivial. Things got messy and I suppose I forgot.
Anyway, yeah, I agree, it's something the user has to take care of...
As long as they know, or remember. And the git error being silenced
didn't help ;-)
[-- Attachment #2: Type: text/html, Size: 2239 bytes --]
next prev parent reply other threads:[~2022-11-04 20:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 18:24 emacs-repository-{version|branch} on Windows Juanma Barranquero
2022-11-04 18:36 ` Juanma Barranquero
2022-11-04 18:51 ` Eli Zaretskii
2022-11-04 18:58 ` Juanma Barranquero
2022-11-04 19:28 ` Stefan Monnier
2022-11-04 20:08 ` Juanma Barranquero
2022-11-04 20:29 ` Eli Zaretskii
2022-11-04 20:42 ` Juanma Barranquero [this message]
2022-11-04 20:47 ` Stefan Monnier
2022-11-04 20:56 ` Eli Zaretskii
2022-11-04 21:09 ` Juanma Barranquero
2022-11-04 21:20 ` Stefan Monnier
2022-11-05 6:24 ` Eli Zaretskii
2022-11-05 11:43 ` Juanma Barranquero
2022-11-05 12:36 ` Eli Zaretskii
2022-11-05 13:20 ` Juanma Barranquero
2022-11-05 15:19 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAeL0SR7c3HfuJ_b+=dXvsoAwRUNXH8aGpnzPCL8yxL=3oA5=Q@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).