All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Cc: Denis Bueno <dbueno@gmail.com>
Subject: [PATCH 0/4] Add 'core.fsyncobjectfiles' config option
Date: Wed, 18 Jun 2008 15:29:48 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806181524490.2907@woody.linux-foundation.org> (raw)


So these four patches end up adding support for conditionally enabling 
fsync() on loose object creation in the .gitconfig file with something 
like

	[core]
		FsyncObjectFiles = true

which can be useful on filesystems that don't already guarantee data 
consistency for other reasons (whether due to ordered writes or due to 
full data journalling).

Actually, just the last one adds the fairly trivial feature, the three 
first patches are just cleanups of the config parsing that I needed in 
order to not gouge my eyes out when looking at the code. The config file 
parser is kind of ad-hoc and people have added more and more options to it 
without ever trying to clean it up, and I refuse to do that.

The full patch-series is

  Split up default "core" config parsing into helper routine
  Split up default "user" config parsing into helper routine
  Split up default "i18n" and "branch" config parsing into helper
    routines
  Add config option to enable 'fsync()' of object files

resulting in the following diffstat:

 Documentation/config.txt |    8 ++++
 cache.h                  |    1 +
 config.c                 |   82 ++++++++++++++++++++++++++++++++++-----------
 environment.c            |    1 +
 sha1_file.c              |    3 +-
 5 files changed, 74 insertions(+), 21 deletions(-)

and the patches themselves will follow..

			Linus

             reply	other threads:[~2008-06-18 22:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 22:29 Linus Torvalds [this message]
2008-06-18 22:30 ` [PATCH 1/4] Split up default "core" config parsing into helper routine Linus Torvalds
2008-06-18 22:31   ` [PATCH 2/4] Split up default "user" " Linus Torvalds
2008-06-18 22:31     ` [PATCH 3/4] Split up default "i18n" and "branch" config parsing into helper routines Linus Torvalds
2008-06-18 22:32       ` [PATCH 4/4] Add config option to enable 'fsync()' of object files Linus Torvalds
2008-06-18 22:49   ` [PATCH 1/4] Split up default "core" config parsing into helper routine Jeff King
2008-06-18 22:58     ` Linus Torvalds
2008-06-18 23:13       ` Jeff King
2008-06-18 23:34         ` Linus Torvalds
2008-06-19  0:08           ` Jeff King
2008-06-19  0:23             ` Linus Torvalds
2008-06-19  0:28               ` Linus Torvalds
2008-06-19  2:10                 ` Daniel Barkalow
2008-06-19  0:32               ` Junio C Hamano
2008-06-19  1:23               ` Jeff King
2008-06-19  0:18           ` Eric Raible

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=alpine.LFD.1.10.0806181524490.2907@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=dbueno@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.