Re: Git status update

2019-10-24 Thread sebb
On Thu, 24 Oct 2019 at 12:54, Emmanuel Bourg wrote: > > Le 24/10/2019 à 12:54, sebb a écrit : > > > Without a fixed tag pointing to a commit, AIUI the commit can be > > eliminated through a force push. > > Force pushing a branch doesn't erase the tags along it nor its parent > commits. The commit

Re: Git status update

2019-10-24 Thread Emmanuel Bourg
Le 24/10/2019 à 12:54, sebb a écrit : > Without a fixed tag pointing to a commit, AIUI the commit can be > eliminated through a force push. Force pushing a branch doesn't erase the tags along it nor its parent commits. The commit and the tag still exist in the repository. > That is deliberate,

Re: Git status update

2019-10-24 Thread sebb
On Thu, 24 Oct 2019 at 09:28, Emmanuel Bourg wrote: > > Le 09/09/2019 à 17:29, Gary Gregory a écrit : > > > What I meant is that, when we successfully create a release, then the > > release tag should go under 'rel/' instead of ''. Sorry for the > > misunderstanding. > > If the vote mail mentions

Re: Git status update

2019-10-24 Thread Emmanuel Bourg
Le 09/09/2019 à 17:29, Gary Gregory a écrit : > What I meant is that, when we successfully create a release, then the > release tag should go under 'rel/' instead of ''. Sorry for the > misunderstanding. If the vote mail mentions the tag name and the commit hash I don't see the need to use read-o

Re: Git status update

2019-09-09 Thread Gary Gregory
e release process is to > > > add a new step at the end to create the rel/tag from the commit SHA. > > > > > > We should be very careful about changing anything in the POM, lest it > > > causes the rel/tag to be created before the RC has been approved. > >

Re: Git status update

2019-09-09 Thread sebb
should be very careful about changing anything in the POM, lest it > > causes the rel/tag to be created before the RC has been approved. > > > > Thoughts? > > > > S. > > -- Forwarded message - > > From: David Nalley > > Date: Sun, 10 Jan

Re: Git status update

2019-09-09 Thread Gary Gregory
> add a new step at the end to create the rel/tag from the commit SHA. > > We should be very careful about changing anything in the POM, lest it > causes the rel/tag to be created before the RC has been approved. > > Thoughts? > > S. > -- Forwarded message

Fwd: Git status update

2019-09-06 Thread sebb
changing anything in the POM, lest it causes the rel/tag to be created before the RC has been approved. Thoughts? S. -- Forwarded message - From: David Nalley Date: Sun, 10 Jan 2016 at 18:00 Subject: Git status update To: infrastruct...@apache.org Greeting PMCs: (bcc to p