> So a common idiom is to put an
> object into the repository and then make a tag (usually annotated)
> pointing to it:
>  $ git tag -a my-big-file $(git hash-object -w my-big-file)
> The `git hash-object -w` command will read the specified file, put it
> into the repo and print the SHA-1 hash calculated over its contents.
> The `git tag -a` command then creates a tag (named "my-big-file")
> pointing to that hash.
> The upside of this approach is that it's simple and elegant: you have
> the file in the repo, and when you want its contents, you simply
> extract it to produce whatever file you want:
>  $ git cat-file my-big-file^{} >/some/path/to/my-big-file

Oh, that is so nice.
1. How did you piece this together 
2. How did you manage to understand the documentation well enough to understand 
that this would even work?

I don't think I've seen "hash-object" mentioned, yet it's such an obvious 
underlying tool that has to be there somewhere.

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.

Reply via email to