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" wrote:
Ok Alex, although I use to restart periodically about 1 time per
day...maybe this time was more time
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 ()
escribió:
> Hi Carlos,
>
> I haven't tried any GUI tools for Git. I'm sure SourceTree is generally
> fine, but many of
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
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
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.
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
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, "carlosrov...@apache.org" wrote:
This is an automated email from the ASF dual-hosted git repository.
