Ramkumar Ramachandra wrote:
> What's so confusing about it?
[...]
> revision:: A particular state of files and directories which was
> stored in the object database. It is referenced by a commit object.
So a revision is a tree? ("one of the things pointed to by a commit
object, representing a pa
Jonathan Nieder writes:
> Ramkumar Ramachandra wrote:
>
>> First, and are ways to specify "revisions", not
>> "commits", as gitrevisions.txt would indicate.
>
> What's the difference between a revision and a commit? The definition
> in gitglossary(7) only confuses me.
They are the same, but I
Jonathan Nieder wrote:
> What's the difference between a revision and a commit? The definition
> in gitglossary(7) only confuses me.
What's so confusing about it?
commit:: As a noun: A single point in the Git history; the entire
history of a project is represented as a set of interrelated commit
Ramkumar Ramachandra writes:
> First, and are ways to specify "revisions", not
> "commits", as gitrevisions.txt would indicate. Second,
> '..' is simply indicative of how users would normally
> want to specify the rev spec: it need not conform to this form, and
> can take any form that gitrevi
Ramkumar Ramachandra wrote:
> First, and are ways to specify "revisions", not
> "commits", as gitrevisions.txt would indicate.
What's the difference between a revision and a commit? The definition
in gitglossary(7) only confuses me.
--
To unsubscribe from this list: send the line "unsubscribe
First, and are ways to specify "revisions", not
"commits", as gitrevisions.txt would indicate. Second,
'..' is simply indicative of how users would normally
want to specify the rev spec: it need not conform to this form, and
can take any form that gitrevisions.txt lists. A 'git log :/quuxery'
i
6 matches
Mail list logo
