| 1 |
On 18/01/14 05:57 AM, Martin Vaeth wrote: |
| 2 |
> Robin H. Johnson <robbat2@g.o> wrote: |
| 3 |
>> |
| 4 |
>> FYI: The following repos contained dangling commits/tags/blobs |
| 5 |
>> [...] you are encouraged to push again [...] |
| 6 |
>> user/mv.git (+blobs) |
| 7 |
> |
| 8 |
> I cannot imagine that the suggested "git push" removed orphaned blobs: |
| 9 |
> AFAIK it is not possible to execute commands like "git prune", |
| 10 |
> "git gc --aggressive", or "git repack -a -d" remotely. |
| 11 |
> Perhaps such things should run as a cron job? |
| 12 |
> |
| 13 |
> |
| 14 |
|
| 15 |
From what I know, dangling commits are part of the git workflow if one |
| 16 |
rewrites history. |
| 17 |
|
| 18 |
If you push A -> B -> C, then reset --hard to B, then push, C will be |
| 19 |
dangling on the remote and will not be cleaned until git gc is |
| 20 |
automatically run on the remote, controlled by the gc.auto config |
| 21 |
variable (on by default). |
Archives