This is the mail archive of the
mailing list for the GCC project.
Re: Moving to git
- From: <Paul_Koning at Dell dot com>
- To: <jason at redhat dot com>
- Cc: <law at redhat dot com>, <gcc at gnu dot org>, <jakub at redhat dot com>
- Date: Thu, 20 Aug 2015 20:22:05 +0000
- Subject: Re: Moving to git
- Authentication-results: sourceware.org; auth=none
- References: <55D61512 dot 8010002 at redhat dot com> <55D61B23 dot 3000309 at redhat dot com> <55D63403 dot 4000603 at redhat dot com>
> On Aug 20, 2015, at 4:09 PM, Jason Merrill <email@example.com> wrote:
> On 08/20/2015 02:23 PM, Jeff Law wrote:
>> ...As far as the trunk and release branches, are there any best practices
>> out there that we can draw from? Obviously doing things like
>> push-rebase-push is bad. Presumably there's others.
> Absolutely, a non-fast-forward push is anathema for anything other people might be working on. The git repository already prohibits this; people that want to push-rebase-push their own branches need to delete the branch before pushing again.
> There are many opinions about best practices, but I don't think any of them are enough better than what we already do to justify a change.
Let's make sure the procedures that people are supposed to follow are clearly documented. I recently went looking for the equivalent in the binutils/gdb project and it doesn't seem to be written down there, though if you ask enough questions on the mailing list you do get some answers.