public inbox for
 help / color / mirror / Atom feed
From: Georg-Johann Lay <>
Subject: Help with git write access.
Date: Thu, 18 May 2023 15:09:44 +0200	[thread overview]
Message-ID: <> (raw)


since quite some time now I did not make changes to the GCC repo.
The last time was actually under SVN and with a different PC.

Following I set up the remote

url = git+ssh://

My MAINTAINERS status is "Write after Approval", and I have
signed a copyright assignment around 2010 and did quite some
changes to the AVR realm.

So I have a bunch of questions and need some help.

1. Setting up git+ssh

The gitwrite page mentions ssh-agent and ssh-add to be used
to set up secure connection, but I can't figure out the
options that I have to provide the these tools.

I am on Ubuntu 22.04.2 LTS, Linux 5.11.0-27-generic, x86-64.

Could you walk me through the exact process please to set up
ssh and git properly?

2. How to commit / push

This was easy under SVN, but with git there are much more ways
to shoot ones knees or violate policies.  If possible I would
fuse all my commits for one PR to a single stage so that my
local commit history won't show up on the remote.  Is there
a wiki or tutorial on the exact steps to use for GCC?

3. ChangeLogs

As far as I understand, ChangeLogs are now auto-extracted from
git logs.  In the old days, I would prepend the folder to
which the changelog will go to the actual changelog entry like:

<tab>* Fix typo.

Is that enough so the tools find their way to gcc/ChangeLog?

Thank you so much,


             reply	other threads:[~2023-05-18 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 13:09 Georg-Johann Lay [this message]
2023-05-18 13:22 ` Frank Ch. Eigler

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:

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

  git send-email \ \ \ \

* 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).