Attempt tp push the new repo

Attempt tp push the new repo

[Eric S. Raymond]

Attempting to push the new repo failed.

sr@snark:/home3/esr/emacs-conversion/emacs-git$ git push
To esr@git.sv.gnu.org:/srv/git/emacs.git
 ! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'esr@git.sv.gnu.org:/srv/git/emacs.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Bob Proulx, you said on 15 Jan you could cleear the old repo out of the way.  
Would you do that, please?
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

The American Republic will endure, until politicians realize they can
bribe the people with their own money.
	-- Alexis de Tocqueville

Re: Attempt tp push the new repo

[Bob Proulx]

Eric S. Raymond wrote:
> Bob Proulx, you said on 15 Jan you could cleear the old repo out of the way.  
> Would you do that, please?

Yes I can do it.  Since you are now requesting it I have done it.
Done.  The emacs git repository has been emptied.  Let me know if
there is any problem.

I can also set up email commit notifications too.  I will hold off
doing that until the repository has been initialized.  It wouldn't be
good to have the entire history sent as email upon upload.

I am sure there will be other tweaks needed too.  Please continue to
CC me since I am not reading the mailing list.

Bob

Re: Attempt tp push the new repo

[Eric S. Raymond]

Bob Proulx <bob@proulx.com>:
> Eric S. Raymond wrote:
> > Bob Proulx, you said on 15 Jan you could cleear the old repo out of the way.  
> > Would you do that, please?
> 
> Yes I can do it.  Since you are now requesting it I have done it.
> Done.  The emacs git repository has been emptied.  Let me know if
> there is any problem.
> 
> I can also set up email commit notifications too.  I will hold off
> doing that until the repository has been initialized.  It wouldn't be
> good to have the entire history sent as email upon upload.
> 
> I am sure there will be other tweaks needed too.  Please continue to
> CC me since I am not reading the mailing list.
> 
> Bob

Repository push is happening now. Thanks for clearing the obstacle.

I will send mail to you and the dev list when the push is done and I
have re-cloned to verify it.

At that time we will also need this cookie droppoed in the repo config:

[receive]
	denynonfastforwards = true
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Re: Attempt tp push the new repo

[Dmitry Gutov]

Hi Eric,

You seem to have forgotten to CC Bob as he asked.

"Eric S. Raymond" <esr@thyrsus.com> writes:
> Repository push is happening now. Thanks for clearing the obstacle.
>
> I will send mail to you and the dev list when the push is done and I
> have re-cloned to verify it.
>
> At that time we will also need this cookie droppoed in the repo config:
>
> [receive]
> 	denynonfastforwards = true

Re: Attempt tp push the new repo

[Lars Magne Ingebrigtsen]

Bob Proulx <bob@proulx.com> writes:

> I can also set up email commit notifications too.  I will hold off
> doing that until the repository has been initialized.  It wouldn't be
> good to have the entire history sent as email upon upload.

It looks like there were no email notifications from the last couple of
commits, so perhaps this hasn't been switched on yet?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Attempt tp push the new repo

[Bob Proulx]

Lars Magne Ingebrigtsen wrote:
> Bob Proulx writes:
> > I can also set up email commit notifications too.  I will hold off
> > doing that until the repository has been initialized.  It wouldn't be
> > good to have the entire history sent as email upon upload.
> 
> It looks like there were no email notifications from the last couple of
> commits, so perhaps this hasn't been switched on yet?

Have you guys been talking on the mailing list but forgetting to CC me
on things you want me to do for you? :-)

I was still waiting for the repository to be uploaded to again.
Otherwise every commit in the history would be seen as new and would
email the result out to the mailing list.  That wouldn't be good.

Therefore I was waiting for someone to tell me that the large uploads
were finished before turning on commit notifications.  And I see in
another message that the initial uploads might not be done yet.  So I
will keep waiting.

Bob

Re: Attempt tp push the new repo

[Lars Magne Ingebrigtsen]

Bob Proulx <bob@proulx.com> writes:

> Therefore I was waiting for someone to tell me that the large uploads
> were finished before turning on commit notifications.  And I see in
> another message that the initial uploads might not be done yet.  So I
> will keep waiting.

If I understand correctly, if we decide to do another Big Conversion Day
(and I think we shouldn't), it won't be any time soon.  In the mean
time, commit messages should be turned off for the changes that are
committed now.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Attempt tp push the new repo

[Bob Proulx]

Lars Magne Ingebrigtsen wrote:
> If I understand correctly, if we decide to do another Big Conversion Day
> (and I think we shouldn't), it won't be any time soon. 

I will let you guys discuss what you want to do and come to a
decision.  I am happy to help with anything you decide upon.

> In the mean time, commit messages should be turned off for the
> changes that are committed now.

They are currently off at this time.  Changes committed now won't have
a notification.  That is the default for new repositories.  Let me
know when you want them enabled and I will add the commit notification
hooks.

Bob

Re: Attempt tp push the new repo

[Eric S. Raymond]

Bob Proulx <bob@proulx.com>:
> Therefore I was waiting for someone to tell me that the large uploads
> were finished before turning on commit notifications.  And I see in
> another message that the initial uploads might not be done yet.  So I
> will keep waiting.

It's all done,  You can enable email commits.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Re: Attempt tp push the new repo

[Bob Proulx]

Eric S. Raymond wrote:
> Bob Proulx <bob@proulx.com>:
> > Therefore I was waiting for someone to tell me that the large uploads
> > were finished before turning on commit notifications.  And I see in
> > another message that the initial uploads might not be done yet.  So I
> > will keep waiting.
> 
> It's all done,  You can enable email commits.

Done!  (Multiple messages read perhaps out of order.)  It is set up
and configured now.  You will start seeing them upon the next commit.

Bob

Re: Attempt tp push the new repo

[Eric S. Raymond]

Bob Proulx <bob@proulx.com>:
> Eric S. Raymond wrote:
> > Bob Proulx <bob@proulx.com>:
> > > Therefore I was waiting for someone to tell me that the large uploads
> > > were finished before turning on commit notifications.  And I see in
> > > another message that the initial uploads might not be done yet.  So I
> > > will keep waiting.
> > 
> > It's all done,  You can enable email commits.
> 
> Done!  (Multiple messages read perhaps out of order.)  It is set up
> and configured now.  You will start seeing them upon the next commit.
> 
> Bob

Thanks.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>