git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] tar-tree: add the "tar.applyUmask" config option

From
Willy Tarreau <w@1wt.eu>
Date
Jul 19, 2006, 22:50 UTC
Message-ID
<20060719225021.GA28591@1wt.eu>
In-Reply-To
<7vd5c1jkc3.fsf@assigned-by-dhcp.cox.net>
On Wed, Jul 19, 2006 at 03:33:48PM -0700, Junio C Hamano wrote:
Show 17 quoted lines
> Willy Tarreau <w@1wt.eu> writes:
> 
> > While I agreed with Linus that the very permissive file modes set in tar
> > archives were not particularly a problem for kernel users, I'm finding
> > that for some other projects it sometimes becomes really annoying, to
> > the point that I finally considered using a plain tar instead. This is a
> > shame because tar-tree is really fast an powerful, and I like its ability
> > to enforce permissions when those of the local dir might be wrong for
> > various reasons.
> 
> I do not have problem with an option to allow a non-default
> behaviour in this area.  Maybe we might want to be able to set
> the mask in the configuration file as well, perhaps like...
> 
> 	tar.umask = user ;# use from the current process'
>         tar.umask = 0    ;# same as default
>         tar.umask = 002  ;# group friendly

This is an excellent idea. I will try to find some spare time tomorrow to implement it. I've also seen the proposal about the --umask= option. I don't think it's absolutely necessary since the umask has little reason to change during the repo's life, but if the implementation is obvious, I will do it too.

Thanks for your suggestion, Willy

Previous: Junio C HamanoNext: Willy Tarreau
Message 3 of 9 in “tar-tree: add the "tar.applyUmask" config option”
  1. tar-tree: add the "tar.applyUmask" config optionWilly Tarreau, Jul 19, 2006
  2. Junio C HamanoJul 19, 2006
  3. Willy TarreauJul 19, 2006
  4. Willy TarreauJul 20, 2006
  5. Rogan DawesJul 20, 2006
  6. Willy TarreauJul 20, 2006
  7. Johannes SchindelinJul 19, 2006
  8. Rene ScharfeJul 20, 2006
  9. Junio C HamanoJul 24, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.