From: Alexander Litvinov <lan@academsoft•ru>
To: Linus Torvalds <torvalds@osdl•org>
Cc: Junio C Hamano <junkio@cox•net>, git@vger•kernel.org
Subject: Re: Security problem
Date: Fri, 16 Jun 2006 15:18:46 +0700 [thread overview]
Message-ID: <200606161518.47149.lan@academsoft.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0606152300460.5498@g5.osdl.org>
> So git certainly gives you the option to be really anal, and doesn't even
> make it needlessly hard or expensive, even with large repositories.
Thanks for detailed description. Now I can sleep without any worry about my
repo :-)
prev parent reply other threads:[~2006-06-16 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606151709.22752.lan@academsoft.ru>
2006-06-16 0:12 ` Security problem Junio C Hamano
2006-06-16 2:28 ` Linus Torvalds
[not found] ` <200606160931.29553.lan@academsoft.ru>
2006-06-16 2:56 ` Linus Torvalds
2006-06-16 3:54 ` Alexander Litvinov
2006-06-16 5:00 ` Linus Torvalds
2006-06-16 5:37 ` Alexander Litvinov
2006-06-16 6:27 ` Linus Torvalds
2006-06-16 8:18 ` Alexander Litvinov [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=200606161518.47149.lan@academsoft.ru \
--to=lan@academsoft$(echo .)ru \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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