On Sun, Jun 29, 2014 at 03:05:48PM -0400, David Nalley wrote:
> You can delete tags and push the deletion to origin.
I stand corrected... ;-)
162ea957e6f02e56f2de7a639f4c7e593b1b3e72 is the new commit-id. I
forgot I wouldn't create the tag so it's there. The commit-id is what
counts anyway.
please all go for it, (creating a vote thread in the morning, provided
Costa Rica goes through, otherwise it will be afternoon, I'm sure)
Daan
On S
I just created a 4.4.0-RC1 and then
$ git push origin 4.4.0-RC1
$ git push origin :4.4.0-RC1
it was deleted cleanly, but I will not create a 4.4.0 untill the vote
passes. I think we need to recreate as Ian is busy on a fix.
On Sun, Jun 29, 2014 at 9:05 PM, David Nalley wrote:
> You can delete ta
You can delete tags and push the deletion to origin.
That said, it gets messy when there are multiple 4.4.0 tags created
and deleted, especially for people not instantly consuming the repo
all of the time.
--David
On Sun, Jun 29, 2014 at 2:47 PM, Chip Childers wrote:
> On Sun, Jun 29, 2014 at 1
On Sun, Jun 29, 2014 at 11:57:06AM +0200, Daan Hoogland wrote:
> LS,
>
> this out of uncertainty on what I produced:
>
> e0f2f5bd14546c5e3bd096a1043d1b73eb464e55 is the commit id on an rc
> branch it is also tagged as 4.4.0.
>
> I have not produced any of the other artifacts like rpm/deb/doc
>
LS,
this out of uncertainty on what I produced:
e0f2f5bd14546c5e3bd096a1043d1b73eb464e55 is the commit id on an rc
branch it is also tagged as 4.4.0.
I have not produced any of the other artifacts like rpm/deb/doc
please have a look/do your part/advice on what to do before starting a
vote. I wi
