Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
URL Rewriter Bot
URL Rewriter Bot

In an answer to a question about the internal format of git’s tree objectsanswer to a question about the internal format of git’s tree objects, to get to one particular tree object that was stored in a pack, I unpacked all of the objects in a repository’s packfiles using git unpack-objects. That seems like overkill. Yes, I realize that commands such git show --raw, git ls-tree, or git cat-file will get close to the internal format.

How do I make git output a single object in its internal format — complete with blob, tree, commit, or tag header — regardless of whether it is stored in loose or packed format?

In an answer to a question about the internal format of git’s tree objects, to get to one particular tree object that was stored in a pack, I unpacked all of the objects in a repository’s packfiles using git unpack-objects. That seems like overkill. Yes, I realize that commands such git show --raw, git ls-tree, or git cat-file will get close to the internal format.

How do I make git output a single object in its internal format — complete with blob, tree, commit, or tag header — regardless of whether it is stored in loose or packed format?

In an answer to a question about the internal format of git’s tree objects, to get to one particular tree object that was stored in a pack, I unpacked all of the objects in a repository’s packfiles using git unpack-objects. That seems like overkill. Yes, I realize that commands such git show --raw, git ls-tree, or git cat-file will get close to the internal format.

How do I make git output a single object in its internal format — complete with blob, tree, commit, or tag header — regardless of whether it is stored in loose or packed format?

Refined question to avoid confusion
Source Link
Greg Bacon
  • 138k
  • 34
  • 192
  • 250

How todo I unpack a single git object?

In an answer to a question about the internal format of git’s tree objects, to get to one particular tree object that was stored in a pack, I unpacked all of the objects in a repository’s packfiles in their entirety using git unpack-objects — all to directly access a single tree object in loose format under .git/objects.

  That seems like overkill. Yes, I realize that commands such git show --raw, git ls-tree, or git cat-file will get close to the internal format. 

How cando I make git output a single object, in its internal format — complete with blob, tree, commit, or tag header — regardless of whether it is stored in loose or packed format?

How to I unpack a single git object?

In an answer to a question about the internal format of git’s tree objects, I unpacked a repository’s packfiles in their entirety using git unpack-objects — all to directly access a single tree object in loose format under .git/objects.

  Yes, I realize that commands such git show --raw, git ls-tree, or git cat-file will get close to the internal format. How can I make git output a single object, complete with blob, tree, commit, or tag header?

How do I unpack a single git object?

In an answer to a question about the internal format of git’s tree objects, to get to one particular tree object that was stored in a pack, I unpacked all of the objects in a repository’s packfiles using git unpack-objects. That seems like overkill. Yes, I realize that commands such git show --raw, git ls-tree, or git cat-file will get close to the internal format. 

How do I make git output a single object in its internal format — complete with blob, tree, commit, or tag header — regardless of whether it is stored in loose or packed format?

Source Link
Greg Bacon
  • 138k
  • 34
  • 192
  • 250

How to I unpack a single git object?

In an answer to a question about the internal format of git’s tree objects, I unpacked a repository’s packfiles in their entirety using git unpack-objects — all to directly access a single tree object in loose format under .git/objects.

Yes, I realize that commands such git show --raw, git ls-tree, or git cat-file will get close to the internal format. How can I make git output a single object, complete with blob, tree, commit, or tag header?