From: Matthias Urlichs <smurf@smurf.noris.de>
To: git@vger.kernel.org
Subject: Re: [RFC][PATCH] Rewriting revs in place in push target repository
Date: Sun, 14 Aug 2005 12:02:42 +0200 [thread overview]
Message-ID: <pan.2005.08.14.10.02.41.120567@smurf.noris.de> (raw)
In-Reply-To: 20050814022011.GA19897@taniwha.stupidest.org
Hi, Chris Wedgwood wrote:
> On Sat, Aug 13, 2005 at 11:47:25PM +0200, Petr Baudis wrote:
>
>> I think it does not in real setups, since thanks to O_RDWR the
>> file should be overwritten only when the write() happens.
>> Can a 41-byte write() be non-atomic in any real conditions?
>
> if you journal metadata only you can see a file extended w/o having
> the block flushed
??? but the file is *not* extended. Also, whether or not a block is
flushed should only matter if the machine crashes ..?
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
CONS [from LISP] 1. v. To add a new element to a list. 2. CONS UP:
v. To synthesize from smaller pieces: "to cons up an example".
-- From the AI Hackers' Dictionary
prev parent reply other threads:[~2005-08-14 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 21:47 [RFC][PATCH] Rewriting revs in place in push target repository Petr Baudis
2005-08-13 22:20 ` Linus Torvalds
2005-08-14 0:55 ` Junio C Hamano
2005-08-14 2:10 ` Linus Torvalds
2005-09-15 17:16 ` Petr Baudis
2005-08-14 2:20 ` Chris Wedgwood
2005-08-14 10:02 ` Matthias Urlichs [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2005.08.14.10.02.41.120567@smurf.noris.de \
--to=smurf@smurf.noris.de \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).