Kunal, Colloquially, in general chat, a commit and a revision are roughly synonymous. Technically, a revision is any object in the object store, especially when known by its hash value. Mots of the time you don't particularly care about all the file content hashes, the directory tree hashes, or even the tag hashes. These (hashes) are all neatly hidden behind 'commits'.
Try `git help revisions` to see the manual page that shows all the different ways that one can name a revision, starting at the hash value, and working up to the various 'ref' (reference) formats (some times a name may point at a specific revision and stay there, and other sorts of reference pointers may move, e.g. a branch name, will point to the *latest *commit on the branch. Note that a commit is the link between the directory tree and file content structure, and the history (parents) structure. the rev-parse allows you also to 'search/find' the right commit in the history. See also `rev-list`. I believe that they always produce lists of hashes, rather than indirect references. This question has been asked before ;-) https://stackoverflow.com/questions/11792538/in-git-what-is-the-difference-between-a-commits-and-a-revisions On Friday, May 15, 2020 at 5:24:16 PM UTC+1, Kunal Chauhan wrote: > > Hi Team, > > From the git doc it is not clear to me > Q :Git commit vs git revision vs git rev_parse > > Q : Usage and scenerio of git commit and git revision > > > > Thanks > Kunal > > > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/dd539df4-3966-46b3-9dcd-5656ac8efcac%40googlegroups.com.
