[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-hackers-public] git: forcing non-fast-forward pushes
From: |
Thomas Schwinge |
Subject: |
Re: [Savannah-hackers-public] git: forcing non-fast-forward pushes |
Date: |
Wed, 11 Feb 2009 12:25:39 +0100 |
User-agent: |
Mutt/1.5.11 |
Hello!
On Tue, Feb 10, 2009 at 11:20:06PM +0100, Sylvain Beucler wrote:
> On Tue, Feb 03, 2009 at 09:03:28PM +0100, Thomas Schwinge wrote:
> > On Tue, Feb 03, 2009 at 08:28:28PM +0100, Sylvain Beucler wrote:
> > > On Tue, Feb 03, 2009 at 01:05:25AM +0100, Thomas Schwinge wrote:
> > > > Has being able to force non-fast-forward pushes (yes, I'm aware of the
> > > > consequences of doing such pushes) been explicitly disabled in the
> > > > Savannah git setup or why does the following fail? (Or is it me doing
> > > > something wrong at this late hour?)
> > > >
> > > > $ git push --force origin master
> > > > Counting objects: 3, done.
> > > > Compressing objects: 100% (2/2), done.
> > > > Writing objects: 100% (3/3), 428 bytes, done.
> > > > Total 3 (delta 0), reused 2 (delta 0)
> > > > To ssh://address@hidden/srv/git/hurd.git
> > > > ! [remote rejected] master -> master (non-fast forward)
> > > > error: denying non-fast forward refs/heads/master (you should pull
> > > > first)
> > > > error: failed to push some refs to
> > > > 'ssh://address@hidden/srv/git/hurd.git'
> > >
> > > This is disabled indeed.
> > > Shared Git repository don't allow that by default.
> >
> > Aha, I see. Hmm. What is the rationale? I mean, isn't the following
> > the exactly equivalent thing? (I've done this just done now.)
>
> Ideally I'd rather not allow history-destructive changes without admin
> moderation. To the least, the current situation prevents beginners
> mistakes.
Yes, that is totally true. And the workaround I described is intuitive
and easy enough, so I don't really bother to have this changed. The only
time where it might indeed become a nuisance is when you publish changes
on branches that are totally work in progress and change frequently or
are rebased often, etc.
> > Also, could you please have the top-level hurd.git repository send commit
> > emails to <address@hidden>, set its owner to <address@hidden> and
> > its description to ``Hurd meta package''?
>
> I got seriously lazy and procrastinated this - but now it's done :)
Thanks! Next time I'll simply open a Savannah support request for such
tiny things so that everyone can see how you are slacking! ;-)
Regards,
Thomas
signature.asc
Description: Digital signature