I'm using git replace command to alter ancestry of commits.
I want to delete merged branch then I suppress the branch parent of the
merge commit.
But, I see that the old reference of replaced commits still exists.
Then my branch is not deleted but hidden. I would like garbage collect it.
There
# alcol...@gmail.com / 2014-09-12 04:49:43 -0700:
I'm using git replace command to alter ancestry of commits.
I want to delete merged branch then I suppress the branch parent of the
merge commit.
But, I see that the old reference of replaced commits still exists.
this reads like you should
From: Alcolo Alcolo alcol...@gmail.com
There is a way to remove all old replaced commits for ever ?
git gc --aggressive works, but you have to purge all the recorded
references to old commits. The ones I know of are:
You have to set core.logallrefupdates to 'false' to prevent logs from
Le vendredi 12 septembre 2014 14:53:13 UTC+2, Roman Neuhauser a écrit :
# alco...@gmail.com javascript: / 2014-09-12 04:49:43 -0700:
I'm using git replace command to alter ancestry of commits.
I want to delete merged branch then I suppress the branch parent of the
merge commit.
Le vendredi 12 septembre 2014 14:59:05 UTC+2, Dale Worley a écrit :
From: Alcolo Alcolo alco...@gmail.com javascript:
There is a way to remove all old replaced commits for ever ?
git gc --aggressive works, but you have to purge all the recorded
references to old commits. The ones I
There are shorthands for going back from HEAD, but not for the initial
commit, AFAICT.
I often want to do this when rebasing, and have come to tagging the
initial commit in my repos with INITIAL.
Is there a better syntax I'm missing?
--
You received this message because you are subscribed to
The only thing I can come up with is this:
$ git rev-list --max-parents=0 HEAD
It can, though, return more than one result if you have multiple
branches from the initial root (e.g. created with git checkout
--orphan). In usual workflows, this should give you a unique ID.
On 12 September 2014
