git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Grimm <koreth@midwinter.com>
To: Dmitry Kakurin <dmitry.kakurin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Windows support
Date: Thu, 26 Jul 2007 13:11:48 +0800	[thread overview]
Message-ID: <46A82D14.6090404@midwinter.com> (raw)
In-Reply-To: <a1bbc6950707251956h3db847c9v8db438f4c665b2cf@mail.gmail.com>

Wrote this reply privately earlier; forwarding to the list at Dmitry's 
suggestion (though it's rendered slightly less relevant by his 
clarifications)...

Dmitry Kakurin wrote:
> This actually answers my question (if it's true).
> If core team is not interested in supporting Windows then I cannot
> trust this system with my source code :-(.
>   

I certainly understand the conclusion, but I'm not sure I would share 
it. Unless you have reason to believe there's something in particular 
about the Windows environment that would cause git to lose data in 
circumstances where it wouldn't do so under UNIX-ish systems, it seems 
like your data should be perfectly safe.

In the year-and-a-bit I've been lurking on the git mailing list and 
making occasional contributions to the code, git has never lost any data 
for anyone to my knowledge. Its design is extremely paranoid in that 
regard, and the paranoia is not really anything platform-dependent. It's 
stuff like, never overwrite files in place (always write a new file 
then, once it's written successfully, get rid of the old one if needed). 
Or, as importantly, keep SHA1 hashes of *everything* and double-check 
them often. Those approaches are just as valid on Windows as on any 
other OS. The SHA1 hashes in particular are pretty unimpeachable, IMO; 
the times people have thought their git repositories have gotten 
corrupted, it has always turned out to be underlying filesystem or disk 
corruption that git's SHA1 checking has caught.

If there are data loss bugs in git (and of course it's possible, even if 
none have been reported to my knowledge) IMO they're vastly more likely 
to be generic than platform-specific.

One nice thing about git is you don't have to take its word for your 
data integrity. You can, without a whole lot of effort, dump out every 
file in the repository and verify that it is what git says it is.

Anyway, I guess my feeling would be, if I were going to choose to not 
use git on Windows it would be because of smoothness of the experience, 
lack of integration with Windows tools, difficult installation process, 
or stuff like that. Data integrity would not even cross my mind as a 
downside of git.

-Steve

  parent reply	other threads:[~2007-07-26  5:11 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 10:35 Windows support Dmitry Kakurin
2007-07-25 10:40 ` Johannes Schindelin
2007-08-02  6:57   ` Asger Ottar Alstrup
2007-08-02 10:45     ` Johannes Schindelin
2007-07-25 11:12 ` Steven Grimm
2007-07-26  2:56   ` Dmitry Kakurin
2007-07-26  3:15     ` Shawn O. Pearce
2007-07-26  6:25       ` Steffen Prohaska
2007-07-26  6:53         ` Shawn O. Pearce
2007-07-26  9:41           ` Marius Storm-Olsen
2007-07-26  9:44             ` Marius Storm-Olsen
2007-07-26  5:11     ` Steven Grimm [this message]
2007-07-25 11:13 ` Steven Grimm
2007-07-25 12:13 ` Nguyen Thai Ngoc Duy
2007-07-25 14:10   ` Johannes Schindelin
2007-07-25 14:15     ` Nguyen Thai Ngoc Duy
2007-07-25 17:13       ` Johannes Schindelin
2007-07-26 13:00       ` Christian MICHON
2007-07-26 13:20         ` Nguyen Thai Ngoc Duy
2007-07-26 13:32           ` Christian MICHON
2007-07-26 13:55             ` Nguyen Thai Ngoc Duy
2007-07-26 15:25               ` Johannes Sixt
2007-07-26  2:26   ` Dmitry Kakurin
2007-07-26  3:06     ` Junio C Hamano
2007-07-26  3:18       ` Shawn O. Pearce
2007-07-26  4:30         ` Junio C Hamano
2007-07-26  5:28           ` Johannes Schindelin
2007-07-26  5:56             ` Han-Wen Nienhuys
2007-07-26  6:40               ` Johannes Schindelin
2007-07-26  7:02                 ` Han-Wen Nienhuys
2007-07-26  7:13                   ` Shawn O. Pearce
2007-07-26  7:18                     ` Han-Wen Nienhuys
2007-07-26 21:39                       ` Jakub Narebski
2007-07-26  7:52                     ` Julian Phillips
2007-07-26 11:29                   ` Nguyen Thai Ngoc Duy
2007-07-26 12:21                     ` Christian MICHON
2007-07-26 12:37                       ` Nguyen Thai Ngoc Duy
2007-07-26 14:37                         ` Johannes Schindelin
2007-07-26 15:07                           ` Nguyen Thai Ngoc Duy
2007-07-26 15:43                             ` Johannes Schindelin
2007-07-26 16:11                               ` Nguyen Thai Ngoc Duy
2007-07-26 18:13                                 ` David Kastrup
2007-07-26 19:39                                   ` Nguyen Thai Ngoc Duy
2007-07-26 20:04                                     ` David Kastrup
2007-07-26 18:18                                 ` Johannes Schindelin
2007-07-26 16:58                             ` Marius Storm-Olsen
2007-07-26 19:43                               ` Nguyen Thai Ngoc Duy
2007-07-26 20:02                                 ` Christian MICHON
2007-07-26  9:11             ` Robin Rosenberg
2007-07-26 10:35               ` Johannes Sixt
2007-07-26  3:38     ` Johannes Schindelin
2007-07-26  3:54       ` Dmitry Kakurin
2007-07-26  4:00       ` Shawn O. Pearce
2007-07-26  5:30         ` Johannes Schindelin
2007-07-26  6:08           ` Henning Rogge
2007-07-26  8:14             ` Andy Parkins
2007-07-25 12:30 ` Steffen Prohaska
2007-07-25 15:34   ` Noel Grandin
2007-07-26  6:46     ` Johannes Schindelin
2007-07-26  6:48       ` Junio C Hamano
2007-07-25 16:58   ` Stephen Cuppett
2007-07-25 17:56     ` Russ Dill
2007-07-25 19:04       ` Medve Emilian-EMMEDVE1
2007-07-25 19:13         ` Russ Dill
2007-07-25 18:43     ` Linus Torvalds
2007-07-25 22:52       ` Wincent Colaiuta
2007-07-26  9:30       ` Marius Storm-Olsen
2007-07-26  3:36     ` Shawn O. Pearce
2007-07-25 17:41 ` Daniel Barkalow

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=46A82D14.6090404@midwinter.com \
    --to=koreth@midwinter.com \
    --cc=dmitry.kakurin@gmail.com \
    --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).