From: Hong Xu <hong@topbug.net>
To: Dmitry Gutov <dgutov@yandex.ru>, 23436@debbugs.gnu.org
Subject: bug#23436: [PATCH] Attemp to use the true name of a file to determine responsible vc if the genuine name does not work.
Date: Wed, 19 Oct 2016 17:16:58 -0700 [thread overview]
Message-ID: <b5e6001a-afc5-08c7-0080-4b2c06f02964@topbug.net> (raw)
In-Reply-To: <5d653522-49bd-8b48-e3d6-0c09d1c65fae@yandex.ru>
[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]
On 10/19/2016 04:58 PM, Dmitry Gutov wrote:
> On 20.10.2016 02:49, Hong Xu wrote:
>> On 10/19/2016 04:37 PM, Dmitry Gutov wrote:
>>> On 19.10.2016 22:33, Hong Xu wrote:
>>>> + (dolist (file-path (list file (file-truename file)))
>>>
>>> Why not just use the true name?
>>
>> Because sometimes we track symlinks specifically. The symlink files may
>> link to a file in a different repo, for example a git submodule.
>
> I'm not sure I understand. Please outline a problem scenario.
mkdir my-repo && cd my-repo
hg init
git clone git://git.savannah.gnu.org/emacs.git
ln -s emacs/README README_emacs
hg add README_emacs
README_emacs is tracked in the repo "my-repo" but README is tracked in
the emacs repo. If true name is directly used, we would fail to obtain
the correct responsible backend.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-20 0:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 21:32 bug#23436: [PATCH] Use the true name of a file to determine responsible vc Hong Xu
2016-10-19 19:19 ` Hong Xu
2016-10-19 19:33 ` bug#23436: [PATCH] Attemp to use the true name of a file to determine responsible vc if the genuine name does not work Hong Xu
2016-10-19 23:37 ` Dmitry Gutov
2016-10-19 23:49 ` Hong Xu
2016-10-19 23:58 ` Dmitry Gutov
2016-10-20 0:16 ` Hong Xu [this message]
2016-10-20 6:58 ` Eli Zaretskii
2016-10-20 7:21 ` Hong Xu
2016-10-20 8:23 ` Eli Zaretskii
2016-10-20 8:50 ` Dmitry Gutov
2016-10-20 9:46 ` Andreas Schwab
2016-10-20 10:02 ` Eli Zaretskii
2016-10-20 10:58 ` Eli Zaretskii
2016-10-20 9:47 ` Dmitry Gutov
2016-10-20 16:39 ` Hong Xu
2016-10-20 22:34 ` Dmitry Gutov
2016-10-20 23:04 ` Hong Xu
2016-10-24 23:41 ` Dmitry Gutov
2016-10-25 19:05 ` Hong Xu
2016-10-25 23:12 ` Dmitry Gutov
2016-10-30 0:42 ` Hong Xu
2016-10-30 16:21 ` Eli Zaretskii
2016-10-30 22:50 ` Hong Xu
2016-10-31 15:43 ` Eli Zaretskii
2016-10-31 19:38 ` Hong Xu
2016-11-01 18:47 ` Eli Zaretskii
2016-11-04 7:46 ` Hong Xu
2016-11-04 10:08 ` Eli Zaretskii
2016-10-31 11:34 ` Dmitry Gutov
2016-10-31 19:24 ` Hong Xu
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=b5e6001a-afc5-08c7-0080-4b2c06f02964@topbug.net \
--to=hong@topbug.net \
--cc=23436@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).