Re: Git Procedure for 2.0.5.1

2012-12-28 Thread Nico Williams
On Fri, Dec 28, 2012 at 6:15 AM, Vincent van Ravesteijn wrote: > Op 27-12-2012 23:27, Nico Williams schreef: > On Dec 27, 2012 3:07 PM, "Vincent van Ravesteijn" wrote: >>> You can correct almost everything with git. Just don't push a wrong tag, >>> ... > >> Right, because deleting a branch or tag

Re: Git Procedure for 2.0.5.1

2012-12-28 Thread Vincent van Ravesteijn
Op 27-12-2012 23:27, Nico Williams schreef: On Dec 27, 2012 3:07 PM, "Vincent van Ravesteijn" > wrote: > You can correct almost everything with git. Just don't push a wrong tag, ... Right, because deleting a branch or tag, or making a branch name refer to a completely d

Re: Git Procedure for 2.0.5.1

2012-12-27 Thread Nico Williams
On Dec 27, 2012 3:07 PM, "Vincent van Ravesteijn" wrote: > You can correct almost everything with git. Just don't push a wrong tag, ... Right, because deleting a branch or tag, or making a branch name refer to a completely different line of commits (e.g., rebase) are destructive operations, but a

Re: Git Procedure for 2.0.5.1

2012-12-27 Thread Nico Williams
On Dec 27, 2012 2:43 PM, "Richard Heck" wrote: > > On 12/27/2012 03:27 PM, Nico Williams wrote: >> >> On Thu, Dec 27, 2012 at 2:18 PM, Richard Heck wrote: >>> >>> So the voting seems to be that we should release a 2.0.5.1, with just the >>> fix for the babel issue. The question now is how, in git

Re: Git Procedure for 2.0.5.1

2012-12-27 Thread Vincent van Ravesteijn
Yes, that is what I am trying to achieve, but I was worried that deleting the 2.0.5.1 branch would invalidate the tag. I guess not? I'm definitely not a git expert. Considering this, there is not much difference between a branch and a tag. "git prune" will prune all unreachable objects using a

Re: Git Procedure for 2.0.5.1

2012-12-27 Thread Richard Heck
On 12/27/2012 03:27 PM, Nico Williams wrote: On Thu, Dec 27, 2012 at 2:18 PM, Richard Heck wrote: So the voting seems to be that we should release a 2.0.5.1, with just the fix for the babel issue. The question now is how, in git, to do this. It's easy enough to do: git checkout tags/2.0.5

Re: Git Procedure for 2.0.5.1

2012-12-27 Thread Nico Williams
On Thu, Dec 27, 2012 at 2:18 PM, Richard Heck wrote: > So the voting seems to be that we should release a 2.0.5.1, with just the > fix for the babel issue. The question now is how, in git, to do this. > > It's easy enough to do: > git checkout tags/2.0.5 > This puts me in "detached head", thou

Git Procedure for 2.0.5.1

2012-12-27 Thread Richard Heck
So the voting seems to be that we should release a 2.0.5.1, with just the fix for the babel issue. The question now is how, in git, to do this. It's easy enough to do: git checkout tags/2.0.5 This puts me in "detached head", though, so I need to create a branch if I want to save anything.