You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@royale.apache.org by ca...@apache.org on 2018/10/01 22:30:28 UTC
[royale-typedefs] annotated tag
org.apache.royale.typedefs-0.9.4-rc1 updated (0774539 -> be658de)
This is an automated email from the ASF dual-hosted git repository.
carlosrovira pushed a change to annotated tag org.apache.royale.typedefs-0.9.4-rc1
in repository https://gitbox.apache.org/repos/asf/royale-typedefs.git.
*** WARNING: tag org.apache.royale.typedefs-0.9.4-rc1 was modified! ***
from 0774539 (commit)
to be658de (tag)
tagging 0774539da3254b59176f16a330aa9b0706cb2e57 (commit)
replaces apache-royale-0.9.2
by Om
on Sun Sep 30 00:08:35 2018 -0700
- Log -----------------------------------------------------------------
[maven-release-plugin] copy for tag org.apache.royale.typedefs-0.9.4-rc1
-----------------------------------------------------------------------
No new revisions were added by this update.
Summary of changes:
Re: [royale-typedefs] annotated tag
org.apache.royale.typedefs-0.9.4-rc1 updated (0774539 -> be658de)
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I would expect once a day is fine, except maybe when there is lots of reverting going on trying to create a release branch.
-Alex
On 10/2/18, 9:40 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Ok Alex, although I use to restart periodically about 1 time per
day...maybe this time was more time up...don't remember.
thanks
El mar., 2 oct. 2018 a las 18:16, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> Hi Carlos,
>
> I haven't tried any GUI tools for Git. I'm sure SourceTree is generally
> fine, but many of the GUIs are caching information. So maybe with all of
> the reverts that have been happening trying to create a release branch that
> SourceTree is getting confused. I think Om may have created and then
> deleted that tag more than once (which is ok when we're trying to cut a
> release branch), and maybe SourceTree doesn't expect that. So it might be
> wise to find out more about SourceTree caching and learn how to flush the
> cache (hopefully as simple as closing and re-opening SourceTree) and flush
> the cache or restart SourceTree more often when we're having problems
> making the release branch.
>
> -Alex
>
> On 10/2/18, 12:49 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
>
> I'm using sourcetree (I think as most of the people out there) , this
> is
> the screen shot:
>
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsnag.gy%2FW6NDEg.jpg&data=02%7C01%7Caharui%40adobe.com%7C0dfb346431f9444cc3f808d62885ce2e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740952484580834&sdata=%2FfpbK%2B2S0HqIuZdtAGyhIH0s1e5iGevgQI09%2Fik23ps%3D&reserved=0
>
> What scares me is that I don't see any commit that reflects this
> commit in
> the screenshot.
> I eve don't have checkout the tag...and never had
>
> So how can I revert something that doesn't show in my interface?
>
> Seriously, this is a complete mystery to me.
>
>
>
>
>
> El mar., 2 oct. 2018 a las 2:07, Alex Harui (<aharui@adobe.com.invalid
> >)
> escribió:
>
> > If you are using some GUI tool for Git, you should find out if it can
> > change tags or not. I don't see how it could have happened via
> command
> > line.
> >
> > The tag change came in my mailbox before the latest commit, so it is
> also
> > possible the tag change was pending. But I didn't compare
> timestamps.
> >
> > But also, I don't think your latest commit was the right thing
> anyway, so
> > you might want to try to revert both the last commit and this tag
> change
> > somehow.
> >
> > Let us know what you find out,
> > -Alex
> >
> > On 10/1/18, 4:55 PM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >
> > Hi Alex,
> > I must to say that don't know what this is really :?
> > I didn't change a tag never, so don't know how this has happen
> > Maybe could be caused to my latest commit? I suppose that Om
> stop for
> > now
> > the release process and revert all.
> >
> > I'm more really surprised of this. So please, let me apologize
> for this
> > whatever way this happen
> >
> > Carlos
> >
> >
> >
> > El mar., 2 oct. 2018 a las 1:47, Alex Harui
> (<aharui@adobe.com.invalid
> > >)
> > escribió:
> >
> > > Changing tags without agreement is, IMO, a bad practice. You
> don't
> > know
> > > how far into the release process we are. It might be too late
> to
> > pick up
> > > the changes.
> > >
> > > -Alex
> > >
> > > On 10/1/18, 3:30 PM, "carlosrovira@apache.org" <
> > carlosrovira@apache.org>
> > > wrote:
> > >
> > > This is an automated email from the ASF dual-hosted git
> > repository.
> > >
> > > carlosrovira pushed a change to annotated tag
> > > org.apache.royale.typedefs-0.9.4-rc1
> > > in repository
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-typedefs.git&data=02%7C01%7Caharui%40adobe.com%7C0dfb346431f9444cc3f808d62885ce2e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740952484580834&sdata=j5%2BgX2iNUGWwHHG%2BtYITKZyurlEqflxYonxMRF6U9qc%3D&reserved=0
> > > .
> > >
> > >
> > > *** WARNING: tag org.apache.royale.typedefs-0.9.4-rc1 was
> > modified! ***
> > >
> > > from 0774539 (commit)
> > > to be658de (tag)
> > > tagging 0774539da3254b59176f16a330aa9b0706cb2e57 (commit)
> > > replaces apache-royale-0.9.2
> > > by Om
> > > on Sun Sep 30 00:08:35 2018 -0700
> > >
> > > - Log
> > -----------------------------------------------------------------
> > > [maven-release-plugin] copy for tag
> > > org.apache.royale.typedefs-0.9.4-rc1
> > >
> >
> -----------------------------------------------------------------------
> > >
> > >
> > > No new revisions were added by this update.
> > >
> > > Summary of changes:
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C0dfb346431f9444cc3f808d62885ce2e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740952484580834&sdata=uE1uKiadX%2FGncFcnWT%2ByaKmkslDInu0syxVwvPOIcy0%3D&reserved=0
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C0dfb346431f9444cc3f808d62885ce2e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740952484590838&sdata=XwbkLERCi7XWfPVrUWGQp9IaoIIZ%2FUsnfy1CtSRKNNQ%3D&reserved=0
>
>
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C0dfb346431f9444cc3f808d62885ce2e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740952484590838&sdata=XwbkLERCi7XWfPVrUWGQp9IaoIIZ%2FUsnfy1CtSRKNNQ%3D&reserved=0
Re: [royale-typedefs] annotated tag org.apache.royale.typedefs-0.9.4-rc1
updated (0774539 -> be658de)
Posted by Carlos Rovira <ca...@apache.org>.
Ok Alex, although I use to restart periodically about 1 time per
day...maybe this time was more time up...don't remember.
thanks
El mar., 2 oct. 2018 a las 18:16, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> Hi Carlos,
>
> I haven't tried any GUI tools for Git. I'm sure SourceTree is generally
> fine, but many of the GUIs are caching information. So maybe with all of
> the reverts that have been happening trying to create a release branch that
> SourceTree is getting confused. I think Om may have created and then
> deleted that tag more than once (which is ok when we're trying to cut a
> release branch), and maybe SourceTree doesn't expect that. So it might be
> wise to find out more about SourceTree caching and learn how to flush the
> cache (hopefully as simple as closing and re-opening SourceTree) and flush
> the cache or restart SourceTree more often when we're having problems
> making the release branch.
>
> -Alex
>
> On 10/2/18, 12:49 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
>
> I'm using sourcetree (I think as most of the people out there) , this
> is
> the screen shot:
>
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsnag.gy%2FW6NDEg.jpg&data=02%7C01%7Caharui%40adobe.com%7Ce914aeba2ed2423938eb08d6283b974a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740633761883242&sdata=Xi5Dfb3whU4XMFC%2FDYmVJBFqHLN2zw7sIpfH15V8uHk%3D&reserved=0
>
> What scares me is that I don't see any commit that reflects this
> commit in
> the screenshot.
> I eve don't have checkout the tag...and never had
>
> So how can I revert something that doesn't show in my interface?
>
> Seriously, this is a complete mystery to me.
>
>
>
>
>
> El mar., 2 oct. 2018 a las 2:07, Alex Harui (<aharui@adobe.com.invalid
> >)
> escribió:
>
> > If you are using some GUI tool for Git, you should find out if it can
> > change tags or not. I don't see how it could have happened via
> command
> > line.
> >
> > The tag change came in my mailbox before the latest commit, so it is
> also
> > possible the tag change was pending. But I didn't compare
> timestamps.
> >
> > But also, I don't think your latest commit was the right thing
> anyway, so
> > you might want to try to revert both the last commit and this tag
> change
> > somehow.
> >
> > Let us know what you find out,
> > -Alex
> >
> > On 10/1/18, 4:55 PM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >
> > Hi Alex,
> > I must to say that don't know what this is really :?
> > I didn't change a tag never, so don't know how this has happen
> > Maybe could be caused to my latest commit? I suppose that Om
> stop for
> > now
> > the release process and revert all.
> >
> > I'm more really surprised of this. So please, let me apologize
> for this
> > whatever way this happen
> >
> > Carlos
> >
> >
> >
> > El mar., 2 oct. 2018 a las 1:47, Alex Harui
> (<aharui@adobe.com.invalid
> > >)
> > escribió:
> >
> > > Changing tags without agreement is, IMO, a bad practice. You
> don't
> > know
> > > how far into the release process we are. It might be too late
> to
> > pick up
> > > the changes.
> > >
> > > -Alex
> > >
> > > On 10/1/18, 3:30 PM, "carlosrovira@apache.org" <
> > carlosrovira@apache.org>
> > > wrote:
> > >
> > > This is an automated email from the ASF dual-hosted git
> > repository.
> > >
> > > carlosrovira pushed a change to annotated tag
> > > org.apache.royale.typedefs-0.9.4-rc1
> > > in repository
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-typedefs.git&data=02%7C01%7Caharui%40adobe.com%7Ce914aeba2ed2423938eb08d6283b974a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740633761883242&sdata=FyiI3qyZaekzbS4cIaYOuiQt7Fa4utF2M7vRV4D2%2FQc%3D&reserved=0
> > > .
> > >
> > >
> > > *** WARNING: tag org.apache.royale.typedefs-0.9.4-rc1 was
> > modified! ***
> > >
> > > from 0774539 (commit)
> > > to be658de (tag)
> > > tagging 0774539da3254b59176f16a330aa9b0706cb2e57 (commit)
> > > replaces apache-royale-0.9.2
> > > by Om
> > > on Sun Sep 30 00:08:35 2018 -0700
> > >
> > > - Log
> > -----------------------------------------------------------------
> > > [maven-release-plugin] copy for tag
> > > org.apache.royale.typedefs-0.9.4-rc1
> > >
> >
> -----------------------------------------------------------------------
> > >
> > >
> > > No new revisions were added by this update.
> > >
> > > Summary of changes:
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ce914aeba2ed2423938eb08d6283b974a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740633761883242&sdata=NU63HxFQih7YgkASXW2MbLKf4UelNpK0V55BCfIq1Ts%3D&reserved=0
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ce914aeba2ed2423938eb08d6283b974a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740633761883242&sdata=NU63HxFQih7YgkASXW2MbLKf4UelNpK0V55BCfIq1Ts%3D&reserved=0
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: [royale-typedefs] annotated tag
org.apache.royale.typedefs-0.9.4-rc1 updated (0774539 -> be658de)
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi Carlos,
I haven't tried any GUI tools for Git. I'm sure SourceTree is generally fine, but many of the GUIs are caching information. So maybe with all of the reverts that have been happening trying to create a release branch that SourceTree is getting confused. I think Om may have created and then deleted that tag more than once (which is ok when we're trying to cut a release branch), and maybe SourceTree doesn't expect that. So it might be wise to find out more about SourceTree caching and learn how to flush the cache (hopefully as simple as closing and re-opening SourceTree) and flush the cache or restart SourceTree more often when we're having problems making the release branch.
-Alex
On 10/2/18, 12:49 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Alex,
I'm using sourcetree (I think as most of the people out there) , this is
the screen shot:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsnag.gy%2FW6NDEg.jpg&data=02%7C01%7Caharui%40adobe.com%7Ce914aeba2ed2423938eb08d6283b974a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740633761883242&sdata=Xi5Dfb3whU4XMFC%2FDYmVJBFqHLN2zw7sIpfH15V8uHk%3D&reserved=0
What scares me is that I don't see any commit that reflects this commit in
the screenshot.
I eve don't have checkout the tag...and never had
So how can I revert something that doesn't show in my interface?
Seriously, this is a complete mystery to me.
El mar., 2 oct. 2018 a las 2:07, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> If you are using some GUI tool for Git, you should find out if it can
> change tags or not. I don't see how it could have happened via command
> line.
>
> The tag change came in my mailbox before the latest commit, so it is also
> possible the tag change was pending. But I didn't compare timestamps.
>
> But also, I don't think your latest commit was the right thing anyway, so
> you might want to try to revert both the last commit and this tag change
> somehow.
>
> Let us know what you find out,
> -Alex
>
> On 10/1/18, 4:55 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
> I must to say that don't know what this is really :?
> I didn't change a tag never, so don't know how this has happen
> Maybe could be caused to my latest commit? I suppose that Om stop for
> now
> the release process and revert all.
>
> I'm more really surprised of this. So please, let me apologize for this
> whatever way this happen
>
> Carlos
>
>
>
> El mar., 2 oct. 2018 a las 1:47, Alex Harui (<aharui@adobe.com.invalid
> >)
> escribió:
>
> > Changing tags without agreement is, IMO, a bad practice. You don't
> know
> > how far into the release process we are. It might be too late to
> pick up
> > the changes.
> >
> > -Alex
> >
> > On 10/1/18, 3:30 PM, "carlosrovira@apache.org" <
> carlosrovira@apache.org>
> > wrote:
> >
> > This is an automated email from the ASF dual-hosted git
> repository.
> >
> > carlosrovira pushed a change to annotated tag
> > org.apache.royale.typedefs-0.9.4-rc1
> > in repository
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-typedefs.git&data=02%7C01%7Caharui%40adobe.com%7Ce914aeba2ed2423938eb08d6283b974a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740633761883242&sdata=FyiI3qyZaekzbS4cIaYOuiQt7Fa4utF2M7vRV4D2%2FQc%3D&reserved=0
> > .
> >
> >
> > *** WARNING: tag org.apache.royale.typedefs-0.9.4-rc1 was
> modified! ***
> >
> > from 0774539 (commit)
> > to be658de (tag)
> > tagging 0774539da3254b59176f16a330aa9b0706cb2e57 (commit)
> > replaces apache-royale-0.9.2
> > by Om
> > on Sun Sep 30 00:08:35 2018 -0700
> >
> > - Log
> -----------------------------------------------------------------
> > [maven-release-plugin] copy for tag
> > org.apache.royale.typedefs-0.9.4-rc1
> >
> -----------------------------------------------------------------------
> >
> >
> > No new revisions were added by this update.
> >
> > Summary of changes:
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ce914aeba2ed2423938eb08d6283b974a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740633761883242&sdata=NU63HxFQih7YgkASXW2MbLKf4UelNpK0V55BCfIq1Ts%3D&reserved=0
>
>
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ce914aeba2ed2423938eb08d6283b974a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740633761883242&sdata=NU63HxFQih7YgkASXW2MbLKf4UelNpK0V55BCfIq1Ts%3D&reserved=0
Re: [royale-typedefs] annotated tag org.apache.royale.typedefs-0.9.4-rc1
updated (0774539 -> be658de)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
I'm using sourcetree (I think as most of the people out there) , this is
the screen shot:
https://snag.gy/W6NDEg.jpg
What scares me is that I don't see any commit that reflects this commit in
the screenshot.
I eve don't have checkout the tag...and never had
So how can I revert something that doesn't show in my interface?
Seriously, this is a complete mystery to me.
El mar., 2 oct. 2018 a las 2:07, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> If you are using some GUI tool for Git, you should find out if it can
> change tags or not. I don't see how it could have happened via command
> line.
>
> The tag change came in my mailbox before the latest commit, so it is also
> possible the tag change was pending. But I didn't compare timestamps.
>
> But also, I don't think your latest commit was the right thing anyway, so
> you might want to try to revert both the last commit and this tag change
> somehow.
>
> Let us know what you find out,
> -Alex
>
> On 10/1/18, 4:55 PM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
> I must to say that don't know what this is really :?
> I didn't change a tag never, so don't know how this has happen
> Maybe could be caused to my latest commit? I suppose that Om stop for
> now
> the release process and revert all.
>
> I'm more really surprised of this. So please, let me apologize for this
> whatever way this happen
>
> Carlos
>
>
>
> El mar., 2 oct. 2018 a las 1:47, Alex Harui (<aharui@adobe.com.invalid
> >)
> escribió:
>
> > Changing tags without agreement is, IMO, a bad practice. You don't
> know
> > how far into the release process we are. It might be too late to
> pick up
> > the changes.
> >
> > -Alex
> >
> > On 10/1/18, 3:30 PM, "carlosrovira@apache.org" <
> carlosrovira@apache.org>
> > wrote:
> >
> > This is an automated email from the ASF dual-hosted git
> repository.
> >
> > carlosrovira pushed a change to annotated tag
> > org.apache.royale.typedefs-0.9.4-rc1
> > in repository
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-typedefs.git&data=02%7C01%7Caharui%40adobe.com%7Cae56999db41b454c130408d627f9673d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740349462428947&sdata=ZpBX%2BvNKLecdpIINysjmwsCK6vcSGT42XQAvgjfk10g%3D&reserved=0
> > .
> >
> >
> > *** WARNING: tag org.apache.royale.typedefs-0.9.4-rc1 was
> modified! ***
> >
> > from 0774539 (commit)
> > to be658de (tag)
> > tagging 0774539da3254b59176f16a330aa9b0706cb2e57 (commit)
> > replaces apache-royale-0.9.2
> > by Om
> > on Sun Sep 30 00:08:35 2018 -0700
> >
> > - Log
> -----------------------------------------------------------------
> > [maven-release-plugin] copy for tag
> > org.apache.royale.typedefs-0.9.4-rc1
> >
> -----------------------------------------------------------------------
> >
> >
> > No new revisions were added by this update.
> >
> > Summary of changes:
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cae56999db41b454c130408d627f9673d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740349462428947&sdata=4Yo5%2BUZnk8dnJWnPVaBOZvz8m%2F014ib%2BnGJj02oNm9s%3D&reserved=0
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: [royale-typedefs] annotated tag
org.apache.royale.typedefs-0.9.4-rc1 updated (0774539 -> be658de)
Posted by Alex Harui <ah...@adobe.com.INVALID>.
If you are using some GUI tool for Git, you should find out if it can change tags or not. I don't see how it could have happened via command line.
The tag change came in my mailbox before the latest commit, so it is also possible the tag change was pending. But I didn't compare timestamps.
But also, I don't think your latest commit was the right thing anyway, so you might want to try to revert both the last commit and this tag change somehow.
Let us know what you find out,
-Alex
On 10/1/18, 4:55 PM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Alex,
I must to say that don't know what this is really :?
I didn't change a tag never, so don't know how this has happen
Maybe could be caused to my latest commit? I suppose that Om stop for now
the release process and revert all.
I'm more really surprised of this. So please, let me apologize for this
whatever way this happen
Carlos
El mar., 2 oct. 2018 a las 1:47, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> Changing tags without agreement is, IMO, a bad practice. You don't know
> how far into the release process we are. It might be too late to pick up
> the changes.
>
> -Alex
>
> On 10/1/18, 3:30 PM, "carlosrovira@apache.org" <ca...@apache.org>
> wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> carlosrovira pushed a change to annotated tag
> org.apache.royale.typedefs-0.9.4-rc1
> in repository
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-typedefs.git&data=02%7C01%7Caharui%40adobe.com%7Cae56999db41b454c130408d627f9673d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740349462428947&sdata=ZpBX%2BvNKLecdpIINysjmwsCK6vcSGT42XQAvgjfk10g%3D&reserved=0
> .
>
>
> *** WARNING: tag org.apache.royale.typedefs-0.9.4-rc1 was modified! ***
>
> from 0774539 (commit)
> to be658de (tag)
> tagging 0774539da3254b59176f16a330aa9b0706cb2e57 (commit)
> replaces apache-royale-0.9.2
> by Om
> on Sun Sep 30 00:08:35 2018 -0700
>
> - Log -----------------------------------------------------------------
> [maven-release-plugin] copy for tag
> org.apache.royale.typedefs-0.9.4-rc1
> -----------------------------------------------------------------------
>
>
> No new revisions were added by this update.
>
> Summary of changes:
>
>
>
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cae56999db41b454c130408d627f9673d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740349462428947&sdata=4Yo5%2BUZnk8dnJWnPVaBOZvz8m%2F014ib%2BnGJj02oNm9s%3D&reserved=0
Re: [royale-typedefs] annotated tag org.apache.royale.typedefs-0.9.4-rc1
updated (0774539 -> be658de)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
I must to say that don't know what this is really :?
I didn't change a tag never, so don't know how this has happen
Maybe could be caused to my latest commit? I suppose that Om stop for now
the release process and revert all.
I'm more really surprised of this. So please, let me apologize for this
whatever way this happen
Carlos
El mar., 2 oct. 2018 a las 1:47, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> Changing tags without agreement is, IMO, a bad practice. You don't know
> how far into the release process we are. It might be too late to pick up
> the changes.
>
> -Alex
>
> On 10/1/18, 3:30 PM, "carlosrovira@apache.org" <ca...@apache.org>
> wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> carlosrovira pushed a change to annotated tag
> org.apache.royale.typedefs-0.9.4-rc1
> in repository
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-typedefs.git&data=02%7C01%7Caharui%40adobe.com%7C2eef8b7effd1415a885b08d627ed7f29%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740298327920871&sdata=Ngss%2BhUx2bcUmXeUgYzrUt8KoF%2BGqYbngSSVBHb2MTI%3D&reserved=0
> .
>
>
> *** WARNING: tag org.apache.royale.typedefs-0.9.4-rc1 was modified! ***
>
> from 0774539 (commit)
> to be658de (tag)
> tagging 0774539da3254b59176f16a330aa9b0706cb2e57 (commit)
> replaces apache-royale-0.9.2
> by Om
> on Sun Sep 30 00:08:35 2018 -0700
>
> - Log -----------------------------------------------------------------
> [maven-release-plugin] copy for tag
> org.apache.royale.typedefs-0.9.4-rc1
> -----------------------------------------------------------------------
>
>
> No new revisions were added by this update.
>
> Summary of changes:
>
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: [royale-typedefs] annotated tag
org.apache.royale.typedefs-0.9.4-rc1 updated (0774539 -> be658de)
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Changing tags without agreement is, IMO, a bad practice. You don't know how far into the release process we are. It might be too late to pick up the changes.
-Alex
On 10/1/18, 3:30 PM, "carlosrovira@apache.org" <ca...@apache.org> wrote:
This is an automated email from the ASF dual-hosted git repository.
carlosrovira pushed a change to annotated tag org.apache.royale.typedefs-0.9.4-rc1
in repository https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-typedefs.git&data=02%7C01%7Caharui%40adobe.com%7C2eef8b7effd1415a885b08d627ed7f29%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740298327920871&sdata=Ngss%2BhUx2bcUmXeUgYzrUt8KoF%2BGqYbngSSVBHb2MTI%3D&reserved=0.
*** WARNING: tag org.apache.royale.typedefs-0.9.4-rc1 was modified! ***
from 0774539 (commit)
to be658de (tag)
tagging 0774539da3254b59176f16a330aa9b0706cb2e57 (commit)
replaces apache-royale-0.9.2
by Om
on Sun Sep 30 00:08:35 2018 -0700
- Log -----------------------------------------------------------------
[maven-release-plugin] copy for tag org.apache.royale.typedefs-0.9.4-rc1
-----------------------------------------------------------------------
No new revisions were added by this update.
Summary of changes: