From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] rev-parse: add option for absolute or relative path formatting
Date: Fri, 6 Nov 2020 01:57:08 +0000 [thread overview]
Message-ID: <20201106015708.GB6252@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20201106005110.GA3479573@google.com>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
On 2020-11-06 at 00:51:10, Jonathan Nieder wrote:
> Ah, thank you. So if I am understanding the above and [1] correctly,
> this means:
>
> - when a path is within a repository, converting it to a path relative
> to the repository root
>
> - when a path is not within a repository, learning so
>
> and that making relative paths with ../../ portion that exits the
> repository is *not* an important part of this use case (though it
> could be useful for other things).
Correct. I felt that adding an --absolute option would be less
beneficial than both an absolute and a relative option, so I implemented
a more generic solution, even though my use case didn't require it.
> Thanks much. I think this tells me enough to understand the series.
Sure, thanks for asking.
--
brian m. carlson (he/him or they/them)
Houston, Texas, US
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2020-11-06 1:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 18:50 [PATCH] rev-parse: add option for absolute or relative path formatting brian m. carlson
2020-09-09 3:23 ` Johannes Schindelin
2020-09-09 22:31 ` brian m. carlson
2020-09-09 14:51 ` SZEDER Gábor
2020-09-09 22:23 ` brian m. carlson
2020-09-10 15:19 ` SZEDER Gábor
2020-09-11 0:03 ` brian m. carlson
2020-11-04 22:16 ` Jonathan Nieder
2020-11-05 3:11 ` brian m. carlson
2020-11-06 0:51 ` Jonathan Nieder
2020-11-06 1:57 ` brian m. carlson [this message]
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201106015708.GB6252@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).