From: Jeff Law <law@redhat.com>
To: Ian Lance Taylor <ian@airs.com>, Iain Buclaw <ibuclaw@gdcproject.org>
Cc: overseers@gcc.gnu.org
Subject: Re: Write after approval access to GCC SVN
Date: Fri, 15 May 2015 14:46:00 -0000 [thread overview]
Message-ID: <555606CD.9020706@redhat.com> (raw)
In-Reply-To: <m3h9re589r.fsf@pepe.airs.com>
On 05/15/2015 06:34 AM, Ian Lance Taylor wrote:
>> Just one question though, is using git-svn a trusted way of pushing in
>> new commits?
>
> Sorry, I don't know.
Yes, I know a number of developers, myself included, are using git-svn
to push commits.
jeff
prev parent reply other threads:[~2015-05-15 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 21:13 Iain Buclaw
2015-05-15 4:50 ` Ian Lance Taylor
2015-05-15 7:11 ` Iain Buclaw
2015-05-15 12:34 ` Ian Lance Taylor
2015-05-15 14:46 ` Jeff Law [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555606CD.9020706@redhat.com \
--to=law@redhat.com \
--cc=ian@airs.com \
--cc=ibuclaw@gdcproject.org \
--cc=overseers@gcc.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).