| 1 |
On Sat, Aug 15, 2015 at 02:44:47PM +0200, Peter Stuge wrote: |
| 2 |
> Hi and happy Git days! :) |
| 3 |
> |
| 4 |
> |
| 5 |
> Robin H. Johnson wrote: |
| 6 |
> > It expands to the hash of the blob of that file; and from that, you can |
| 7 |
> > identify which commits the blob exists in. |
| 8 |
> |
| 9 |
> $ git ls-tree HEAD README |
| 10 |
> 100644 blob 08ae16956b8944da2fef75fee892dcba457cf4f0 README |
| 11 |
> $ |
| 12 |
> |
| 13 |
> $ (stat --printf='blob %s\0' README; cat README) | sha1sum |
| 14 |
> 08ae16956b8944da2fef75fee892dcba457cf4f0 - |
| 15 |
> $ |
| 16 |
> |
| 17 |
> This is so simple to generate that it doesn't really need a |
| 18 |
> placeholder in every ebuild in the repository. |
| 19 |
|
| 20 |
If this is this simple to regenerate, consider my response here a very |
| 21 |
strong +1; let's kill $id$ out of the git repository and generate this |
| 22 |
some how at the rsync level if users need it or give them a tool that |
| 23 |
will generate it. |
| 24 |
|
| 25 |
I don't object to someone having a way to get this information if it |
| 26 |
is useful to them, but I don't think we need a placeholder for it in the |
| 27 |
git repository. |
| 28 |
|
| 29 |
William |
Archives