unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org
Cc: guile-devel <guile-devel@gnu.org>
Subject: git config receive.denyNonFastForwards true on server?
Date: Wed, 16 Jan 2013 10:55:55 +0100	[thread overview]
Message-ID: <87mww9jvtg.fsf@pobox.com> (raw)

Hi,

I was about to ask the savannah folks / gnu admins if they could change
the configuration for guile's repo to allow non-fast-forward pushes
(obviously with the --force or + flag).  This would let me fix the
authorship in the recent PEG merge to master.  It would also make it
easier to update a branch: you wouldn't have to delete it first and then
re-push.  (This doesn't work with master because it is the default ref,
and there is another setting regarding deleting the default ref.)

What do you think?

Andy
-- 
http://wingolog.org/



             reply	other threads:[~2013-01-16  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16  9:55 Andy Wingo [this message]
2013-01-16 12:13 ` git config receive.denyNonFastForwards true on server? Ludovic Courtès
2013-01-21 12:34   ` Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mww9jvtg.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).