This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Committing via git

From: Joel Sherrill <joel dot sherrill at oarcorp dot com>
To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Fri, 26 Feb 2016 13:18:22 -0600
Subject: Re: Committing via git
Authentication-results: sourceware.org; auth=none
References: <CF9C2004-2F37-4382-BC2B-742D152A344F at oarcorp dot com> <CAH6eHdTso08Q=Lev_0K6-NXS1wCO0FoMDTxF=6+xsrBr7+Wa1w at mail dot gmail dot com>



On 2/26/2016 11:50 AM, Jonathan Wakely wrote:

On 26 February 2016 at 17:25, Joel Sherrill wrote:

Hi

Is there something special needed to commit via git? I got an odd error pushing some minor RTEMS patches and wondered what the proper procedure was.

I am using the same commands and process I use with newlib so was wondering.

The website has svn instructions so maybe I am just confused after being up too long.


GCC sources are still subversion. The trunk (aka master) and
gcc-*-branch branches in Git are read-only, you can only push to
personal branches.


Well that would certainly explain why a git push to master didn't work. :)

Sorry for the stupidity.

Thanks.

--joel

Follow-Ups:
- Re: Committing via git
  - From: Jeff Law

References:
- Committing via git
  - From: Joel Sherrill
- Re: Committing via git
  - From: Jonathan Wakely

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]