From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: "Eric Wong" <normalperson@yhbt.net>,
"Johannes Sixt" <j6t@kdbg.org>,
"Jens Lehmann" <Jens.Lehmann@web.de>,
"Git Mailing List" <git@vger.kernel.org>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Michael Haggerty" <mhagger@alum.mit.edu>
Subject: Re: No fchmd. was: Re: [PATCH 00/14] Add submodule test harness
Date: Thu, 10 Jul 2014 14:43:03 -0700 [thread overview]
Message-ID: <xmqqoaww7uvs.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53BEFDA8.7020409@web.de> ("Torsten Bögershausen"'s message of "Thu, 10 Jul 2014 22:55:04 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> On 2014-07-10 21.49, Junio C Hamano wrote:
> []
>> If we limit the case to "Inherit permissions from the file we are
>> replacing by taking a lock on it", which is the topic of discussion
>> in this thread, we do not have to worry about how to configure the
>> value (we do not have to) and adding a new parameter to tell the
>> mode to hold-lock-file-for-update is unneeded (the function will
>> have a pathname of the original and can learn the current permission
>> bits itself).
> So something like this:
Yeah, I think something along those lines may be sufficient and we
do not have to do anything when closing/committing, at least POSIX
systems. I do not know if other filesystems we may care about let
you open with 0400 and still write into it, though.
> (I will probably not have the time to make a proper patch :-(
That's OK. I see many names on Cc: who are all capable of helping
us ;-)
>
> diff --git a/lockfile.c b/lockfile.c
> index 4899270..134d5c8 100644
> --- a/lockfile.c
> +++ b/lockfile.c
> @@ -156,6 +156,11 @@ static void resolve_symlink(struct strbuf *path)
> /* Make sure errno contains a meaningful value on error */
> static int lock_file(struct lock_file *lk, const char *path, int flags)
> {
> + int perms = 0666;
> + struct stat st;
> + if (!lstat(path, &st))
> + perms = st.st_mode & 0777;
> +
> if (!lock_file_list) {
> /* One-time initialization */
> sigchain_push_common(remove_lock_file_on_signal);
> @@ -179,7 +184,7 @@ static int lock_file(struct lock_file *lk, const char *path, int flags)
> if (!(flags & LOCK_NODEREF))
> resolve_symlink(&lk->filename);
> strbuf_addstr(&lk->filename, LOCK_SUFFIX);
> - lk->fd = open(lk->filename.buf, O_RDWR | O_CREAT | O_EXCL, 0666);
> + lk->fd = open(lk->filename.buf, O_RDWR | O_CREAT | O_EXCL, perms);
> if (lk->fd < 0) {
> strbuf_reset(&lk->filename);
> return -1;
prev parent reply other threads:[~2014-07-10 21:43 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 16:56 [PATCH 00/14] Add submodule test harness Jens Lehmann
2014-06-15 16:57 ` [PATCH 01/14] test-lib: add test_dir_is_empty() Jens Lehmann
2014-06-16 22:05 ` Junio C Hamano
2014-06-17 16:47 ` Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-15 16:58 ` [PATCH 02/14] submodules: Add the lib-submodule-update.sh test library Jens Lehmann
2014-06-16 22:49 ` Junio C Hamano
2014-06-17 17:33 ` Jens Lehmann
2014-06-17 18:44 ` Junio C Hamano
2014-06-17 20:46 ` Jens Lehmann
2014-06-17 21:05 ` Junio C Hamano
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-20 17:31 ` Junio C Hamano
2014-07-01 21:24 ` [PATCH v3 " Jens Lehmann
2014-06-15 16:58 ` [PATCH 03/14] checkout: call the new submodule update test framework Jens Lehmann
2014-06-15 16:59 ` [PATCH 04/14] apply: add t4137 for submodule updates Jens Lehmann
2014-06-15 16:59 ` [PATCH 05/14] read-tree: add t1013 " Jens Lehmann
2014-06-15 17:00 ` [PATCH 06/14] reset: add t7112 " Jens Lehmann
2014-06-15 17:01 ` [PATCH 07/14] bisect: add t6041 " Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-15 17:01 ` [PATCH 08/14] merge: add t7613 " Jens Lehmann
2014-06-15 17:02 ` [PATCH 09/14] rebase: add t3426 " Jens Lehmann
2014-06-16 9:57 ` Eric Sunshine
2014-06-17 17:41 ` Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-15 17:02 ` [PATCH 10/14] pull: add t5572 " Jens Lehmann
2014-06-15 17:03 ` [PATCH 11/14] cherry-pick: add t3512 " Jens Lehmann
2014-06-15 17:03 ` [PATCH 12/14] am: add t4255 " Jens Lehmann
2014-06-15 17:04 ` [PATCH 13/14] stash: add t3906 " Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-06-15 17:04 ` [PATCH 14/14] revert: add t3513 " Jens Lehmann
2014-06-19 20:12 ` [PATCH v2 " Jens Lehmann
2014-07-02 14:54 ` [PATCH 00/14] Add submodule test harness Torsten Bögershausen
2014-07-02 19:57 ` Jens Lehmann
2014-07-03 5:56 ` Torsten Bögershausen
2014-07-03 21:14 ` Jens Lehmann
2014-07-07 17:05 ` Junio C Hamano
2014-07-07 19:40 ` Torsten Bögershausen
2014-07-08 19:34 ` Jens Lehmann
2014-07-08 20:25 ` Ramsay Jones
2014-07-08 21:03 ` Ramsay Jones
2014-07-09 6:39 ` No fchmod() under msygit - Was: " Torsten Bögershausen
2014-07-09 20:00 ` Eric Wong
2014-07-14 11:31 ` Erik Faye-Lund
2014-07-14 13:55 ` Nico Williams
2014-07-14 14:02 ` Nico Williams
2014-07-14 19:30 ` Karsten Blees
2014-07-14 21:18 ` Junio C Hamano
2014-07-09 6:14 ` Torsten Bögershausen
2014-07-09 15:20 ` Junio C Hamano
2014-07-09 18:19 ` Jens Lehmann
2014-07-09 19:31 ` Junio C Hamano
2014-07-10 20:52 ` Junio C Hamano
2014-07-12 18:23 ` Jens Lehmann
2014-07-14 1:01 ` Junio C Hamano
2014-07-14 18:22 ` Jens Lehmann
2014-07-14 21:18 ` Junio C Hamano
2014-07-09 17:21 ` Johannes Sixt
2014-07-09 19:22 ` Junio C Hamano
2014-07-09 19:56 ` Eric Wong
2014-07-09 21:57 ` Junio C Hamano
2014-07-10 6:22 ` No fchmd. was: " Torsten Bögershausen
2014-07-10 19:49 ` Junio C Hamano
2014-07-10 20:55 ` Torsten Bögershausen
2014-07-10 21:43 ` Junio C Hamano [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=xmqqoaww7uvs.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=mhagger@alum.mit.edu \
--cc=normalperson@yhbt.net \
--cc=pclouds@gmail.com \
--cc=tboegi@web.de \
/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).