Re: [git-users] Git life cycle

[Michael]

On 2016-05-23, at 8:53 AM, Dale R. Worley  wrote:

> "Philip Oakley"  writes:
>> +1 for the nice explanation.
> 
> Thanks!
> 
>> The Index is also commonly called the *staging area* when viewed from an 
>> outward facing perspective (i.e. what do users do), with index being more 
>> commonly used for an inward facing perspective (e.g. for code development). 
> 
> Thanks; I've added "staging area" to my guide.
> 
>> There is currently a truce about which is the 'right name'! 
> 
> And there's a third contender:  "the cache".
> 
> Of course we can't agree on the terminology to use!
> 
> Dale

Clearly, we need a 4th term that encompasses all of them, and is the universal 
standard :-)

---
Entertaining minecraft videos
http://YouTube.com/keybounce

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Git life cycle

[Dale R. Worley]

"Philip Oakley"  writes:
> +1 for the nice explanation.

Thanks!

> The Index is also commonly called the *staging area* when viewed from an 
> outward facing perspective (i.e. what do users do), with index being more 
> commonly used for an inward facing perspective (e.g. for code development). 

Thanks; I've added "staging area" to my guide.

> There is currently a truce about which is the 'right name'! 

And there's a third contender:  "the cache".

Of course we can't agree on the terminology to use!

Dale

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] How GIT stores data

[Dale R. Worley]

Sharan Basappa  writes:
> I am pretty much new to Git though I am using it for a couple of projects 
> (without much understanding as such).
>
> In Git documents, it is mentioned that Git stores data as a stream of
> snapshots. Compared to other VCS tools, the only difference I am able
> to tell is that Git stores the entire file for each versions while
> other VCS tools might store only differences.
>
> Can someone help me understand this?

Actually, you don't *need* to understand how it's done.  You do need to
understand that Git commands are organized around the idea that commits
are a total copy of your project.

OTOH, you need to be careful.  Some commands, particularly ones
involving merging and "rebase" actually *do* think of commits not as
snapshots but as the difference between the commit and its parent.  That
is how you can "reorder" two commits -- changing the commit order from A
- B - C is actually constructing new commits D and E so that in the new
commit order A - D - E, the difference between A and D is the same as
the difference between B and C, and the difference between D and E is
the difference between A and B.

But even in this situation, what is *stored* is a sequence of commits
(done with sophisticated compression) -- the merge or rebase command
calcuates the differences based on the contents of the old commits, and
then constructs a new set of commits that have the proper differences
between them, and then stores the new commits.

Dale

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Problem:fatal: early EOF fatal: index-pack failed

[Konstantin Khomoutov]

On Fri, 20 May 2016 18:54:44 -0400
wor...@alum.mit.edu (Dale R. Worley) wrote:

[...]
> > remote: fatal: unable to create thread: Resource temporarily
> > unavailable
> 
> The max-connections setting may be unlimited, but that doesn't mean
> that the server daemon can create an enormous number of threads.  The
> last quoted line is the client reporting that the server reported
> that it could not create a new thread.  There are many reasons why
> that might happen.  One possibility is that the server system ran out
> of RAM and swap space.  Another possibility is that the user running
> the server process has a low quota of processes that it is allowed to
> create.

I concur:  pthread_create(3) lists EAGAIN as the error code returned to
signalize the thread creation failure due to shortage of resources
available *or* the system limit for the number of per-process or
per-user threads is hit, and

  $ errno EAGAIN
  EAGAIN 11 Resource temporarily unavailable

which is what Git reports.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.