From: perryh@pluto.rain.com (Perry Hutchison)
To: l.s.r@web.de
Cc: git@vger.kernel.org, mpsuzuki@hiroshima-u.ac.jp
Subject: Re: [PATCH] git-archive: accept --owner and --group like GNU tar
Date: Mon, 01 Jan 2018 16:32:20 -0800 [thread overview]
Message-ID: <5a4ad314.C6wihAr5rEC8jRkB%perryh@pluto.rain.com> (raw)
In-Reply-To: <81b882a5-0c35-f3c4-78e2-d3e36290fec1@web.de>
Ren?? Scharfe <l.s.r@web.de> wrote:
> Am 29.12.2017 um 15:05 schrieb suzuki toshiya:
> > The ownership of files created by git-archive is always
> > root:root. Add --owner and --group options which work
> > like the GNU tar equivalent to allow overriding these
> > defaults.
> ... the receiver would need to be root to set both IDs, or be a
> group member to set the group ID; I guess the latter is more common.
If the received files are owned by root:root as stated, I guess the
receiver must be running as root, no?
next prev parent reply other threads:[~2018-01-02 1:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 14:05 [PATCH] git-archive: accept --owner and --group like GNU tar suzuki toshiya
2018-01-01 18:29 ` René Scharfe
2018-01-02 0:32 ` Perry Hutchison [this message]
2018-01-04 0:43 ` René Scharfe
[not found] ` <df39f62558314cf6a9d9df3e23f31dd8@OS2PR01MB1147.jpnprd01.prod.outlook.com>
2018-01-02 6:58 ` suzuki toshiya
2018-01-02 21:36 ` René Scharfe
[not found] ` <59a1fc058278463996ed68c970a5e08a@OS2PR01MB1147.jpnprd01.prod.outlook.com>
2018-01-04 1:29 ` suzuki toshiya
[not found] ` <955dae095d504b00b3e1c8a956ba852a@OS2PR01MB1147.jpnprd01.prod.outlook.com>
2018-01-04 2:25 ` suzuki toshiya
2018-01-04 16:59 ` René Scharfe
2018-01-04 18:22 ` Junio C Hamano
2018-01-05 13:54 ` René Scharfe
2018-01-05 19:10 ` Junio C Hamano
[not found] ` <2112f9c245d64f4e89361df7e9de9374@OS2PR01MB1147.jpnprd01.prod.outlook.com>
2018-01-05 4:23 ` suzuki toshiya
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=5a4ad314.C6wihAr5rEC8jRkB%perryh@pluto.rain.com \
--to=perryh@pluto.rain.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=mpsuzuki@hiroshima-u.ac.jp \
/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).