From: David Howells <dhowells@redhat.com>
To: chet.ramey@case.edu
Cc: dhowells@redhat.com, Jeffrey E Altman <jaltman@auristor.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Etienne Champetier <champetier.etienne@gmail.com>,
Marc Dionne <marc.dionne@auristor.com>,
Steve French <sfrench@samba.org>,
linux-afs@lists.infradead.org, openafs-devel@openafs.org,
linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] afs, bash: Fix open(O_CREAT) on an extant AFS file in a sticky dir
Date: Wed, 30 Apr 2025 17:14:41 +0100 [thread overview]
Message-ID: <666533.1746029681@warthog.procyon.org.uk> (raw)
In-Reply-To: <473bad0c-9e38-4f8b-9939-c70c52890cd2@case.edu>
Chet Ramey <chet.ramey@case.edu> wrote:
> Well, except for CMU's report.
Do you know of any link for that? I'm guessing that is it was 1992, there may
be no online record of it.
David
next prev parent reply other threads:[~2025-04-30 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 16:37 [PATCH] afs, bash: Fix open(O_CREAT) on an extant AFS file in a sticky dir David Howells
2025-04-29 17:35 ` Jeffrey E Altman
2025-04-30 15:09 ` Chet Ramey
2025-04-30 16:14 ` David Howells [this message]
2025-04-30 17:26 ` Jeffrey E Altman
2025-04-30 18:36 ` Chet Ramey
2025-05-05 13:14 ` Christian Brauner
[not found] ` <CAOdf3grbDQ-Fh2bV7XfoYvVBhgBAh7-hZyyxTNt1RfGekrA-nA@mail.gmail.com>
2025-05-05 14:42 ` Jeffrey E Altman
2025-05-14 12:50 ` Chet Ramey
2025-05-06 10:26 ` David Howells
2025-05-09 10:33 ` Christian Brauner
2025-05-12 13:02 ` [PATCH v2] " David Howells
2025-05-13 7:49 ` Christian Brauner
2025-05-13 8:30 ` David Howells
2025-05-13 15:44 ` Jeffrey E Altman
2025-05-14 12:49 ` [PATCH] " Chet Ramey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=666533.1746029681@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=brauner@kernel.org \
--cc=champetier.etienne@gmail.com \
--cc=chet.ramey@case.edu \
--cc=jaltman@auristor.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=openafs-devel@openafs.org \
--cc=sfrench@samba.org \
--cc=viro@zeniv.linux.org.uk \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox