From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: GIT (was: Coverity Scan)
Date: Sat, 26 Apr 2014 00:42:00 -0000 [thread overview]
Message-ID: <535B00FA.6020500@gmail.com> (raw)
In-Reply-To: <139855391.20140426032748@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On 4/26/2014 07:27, Andrey Repin wrote:
> This is exactly what makes me dislike it strongly. This, and idiotic model of
> copying whole repository to my machine, when I only want to glance at the
> source code, and find the culprit of my current issues.
> I've spent 3 hours downloading a 200Mb repo of a project, where the Subversion
> client pulled 4 or 5Mb HEAD of it in like 10 minutes, once I realized what an
> idiotic weight I pulled and went to google to see if it can be done better.
> And "fine control" doesn't mix with "project consistency" at all.
> Subversion is aimed at versioning of a whole project, in a supposedly
> consistent state at each version. What can be more "fine" than this, is beyond
> my understanding.
git clone --depth 1 if you don't care about history.
> You can still commit separate files from working copy, though, but this
> practice is discouraged for the greater good of the project you develop.
>
Don't you need to git add individual files to mark for commit? Won't you
get into the same problems if you forgot to commit files in SVN?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
next prev parent reply other threads:[~2014-04-26 0:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 15:24 Jim Garrison
2014-04-25 16:22 ` Corinna Vinschen
2014-04-25 20:42 ` Reini Urban
2014-04-26 6:25 ` GIT Christopher Faylor
2014-04-25 21:31 ` GIT Achim Gratz
2014-04-26 19:50 ` GIT Eliot Moss
2014-04-25 23:35 ` GIT (was: Coverity Scan) Andrey Repin
2014-04-26 0:42 ` JonY [this message]
2014-04-26 3:34 ` Duncan Roe
2014-04-26 6:13 ` GIT Achim Gratz
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=535B00FA.6020500@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).