* git config receive.denyNonFastForwards true on server?
@ 2013-01-16 9:55 Andy Wingo
2013-01-16 12:13 ` Ludovic Courtès
0 siblings, 1 reply; 3+ messages in thread
From: Andy Wingo @ 2013-01-16 9:55 UTC (permalink / raw)
To: ludo; +Cc: guile-devel
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/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: git config receive.denyNonFastForwards true on server?
2013-01-16 9:55 git config receive.denyNonFastForwards true on server? Andy Wingo
@ 2013-01-16 12:13 ` Ludovic Courtès
2013-01-21 12:34 ` Andy Wingo
0 siblings, 1 reply; 3+ messages in thread
From: Ludovic Courtès @ 2013-01-16 12:13 UTC (permalink / raw)
To: Andy Wingo; +Cc: guile-devel
Hi,
Andy Wingo <wingo@pobox.com> skribis:
> 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.)
Yeah, I see. The only issue is to make sure non-fast-forward pushes
don’t happen by mistake on the regular branches. But it’s reasonable to
say that we’re all sufficiently disciplined so that won’t happen. So
yes, if you find it helpful, go ahead.
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: git config receive.denyNonFastForwards true on server?
2013-01-16 12:13 ` Ludovic Courtès
@ 2013-01-21 12:34 ` Andy Wingo
0 siblings, 0 replies; 3+ messages in thread
From: Andy Wingo @ 2013-01-21 12:34 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guile-devel
On Wed 16 Jan 2013 13:13, ludo@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Andy Wingo <wingo@pobox.com> skribis:
>
>> 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.)
>
> Yeah, I see. The only issue is to make sure non-fast-forward pushes
> don’t happen by mistake on the regular branches. But it’s reasonable to
> say that we’re all sufficiently disciplined so that won’t happen. So
> yes, if you find it helpful, go ahead.
https://savannah.gnu.org/task/index.php?12428
--
http://wingolog.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-01-21 12:34 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-16 9:55 git config receive.denyNonFastForwards true on server? Andy Wingo
2013-01-16 12:13 ` Ludovic Courtès
2013-01-21 12:34 ` Andy Wingo
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).