all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Glenn Morris <rgm@gnu.org>, 25075@debbugs.gnu.org
Subject: bug#25075: 26.0.50; [PATCH] Dired can now dereference symlinks when copying
Date: Tue, 11 Aug 2020 15:17:18 +0200	[thread overview]
Message-ID: <87d03xwcdd.fsf@gnus.org> (raw)
In-Reply-To: <CAFyQvY1ERBWXtmLuHC1POK+PsSkHDZi5rrChMqCbq-dATF-Lyg@mail.gmail.com> (Kaushal Modi's message of "Thu, 01 Dec 2016 06:06:21 +0000")

Kaushal Modi <kaushal.modi@gmail.com> writes:

> Copying with symlinks dereferenced is almost always the case for me,
> because of the version control system we use. It is a central VCS. So
> we need to check out the files before editing them. In checked-in
> state, all files are just symlinks to the physical versions in a
> central cache server. So almost always "cp -L" is what I want to do
> when copying files from one place to another without checking them
> out. My cp is aliased to "cp -L".

Thanks; I've now applied this patch to Emacs 28, since Eli said:

> That was my first thought as well, but we use the same approach as
> Kaushal proposed for the equivalent of the -p switch to 'cp'.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-08-11 13:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 18:04 bug#25075: 26.0.50; [PATCH] Dired can now dereference symlinks when copying Kaushal Modi
2016-11-30 18:38 ` Eli Zaretskii
2016-11-30 18:42   ` Kaushal Modi
2016-12-01  0:38 ` Glenn Morris
2016-12-01  3:39   ` Eli Zaretskii
2016-12-01  4:12   ` Kaushal Modi
2016-12-01  6:06     ` Kaushal Modi
2020-08-11 13:17       ` Lars Ingebrigtsen [this message]
2019-06-24 23:17   ` Lars Ingebrigtsen

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=87d03xwcdd.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=25075@debbugs.gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=rgm@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.