From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Some local customization enhancements when using git
Date: Mon, 13 Jan 2020 14:02:00 -0000 [thread overview]
Message-ID: <9cffe927-2ac8-ad21-db59-2c3d0f5f3a10@arm.com> (raw)
In-Reply-To: <95dfd77a-3361-545e-8b86-01078304ae29@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
On 10/01/2020 14:26, Richard Earnshaw (lists) wrote:
> On 10/01/2020 13:23, Richard Earnshaw (lists) wrote:
>> This patch is intended to help with folks setting up a git work
>> environment for use with GCC following the transition to git. It
>> currently does a couple of things.
>>
>> 1) Add an alias 'svn-rev' to git so that you can look up a legacy
>> commit by its svn revision number. This enables you to type
>> git svn-rev 1234
>> and git will show the commit log entry relating to SVN r1234.
>>
>> 2) Sets up tracking information for the user's private name area in
>> the git repo. It tries to figure out some sensible answers to the
>> data it needs, but allows the user to override the values. It then
>> creates the fetch and push entries that are needed for tracking the
>> extra refs. This implements one part of the recommendations that I've
>> proposed in svnwrite.html for dealing with private branches.
>>
>> It should be possible to run the script more than once and for it to
>> DTRT. If you change your answers the configuration should be
>> correctly updated.
>>
>> 2020-01-10 Richard Earnshaw <rearnsha@arm.com>
>>
>> Â Â Â Â Â * gcc-git-customization: New file.
>>
>
> Updated to add better support for diff-ing .md files.
>
> R.
A couple more tweaks to this file and I've now checked it in.
1) Added the ability to select the prefix for the personal namespace.
This will be cached. If you change it, then the push operations will be
updated (but any local branches you will have to rename if you want them
to continue working afterwards).
2) Removed the + from the added push spec.
R.
[-- Attachment #2: gcc-git-customization.sh --]
[-- Type: application/x-shellscript, Size: 2312 bytes --]
next prev parent reply other threads:[~2020-01-13 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 13:29 Richard Earnshaw (lists)
2020-01-10 13:30 ` Richard Biener
2020-01-10 14:04 ` Richard Earnshaw (lists)
2020-01-10 14:13 ` Richard Earnshaw (lists)
2020-01-10 14:27 ` Richard Earnshaw (lists)
2020-01-13 12:50 ` [PATCH] contrib: git descr/undescr aliases Jakub Jelinek
2020-01-14 10:18 ` Roman Zhuykov
2020-01-14 10:22 ` Jakub Jelinek
2020-01-14 23:50 ` [PATCH] contrib: git descr/undescr aliases fix for older git Jakub Jelinek
2020-01-15 11:34 ` Richard Earnshaw (lists)
2020-01-14 23:39 ` [PATCH] contrib: git descr/undescr aliases Joseph Myers
2020-01-13 14:02 ` Richard Earnshaw (lists) [this message]
2020-01-13 16:03 ` Some local customization enhancements when using git Richard Earnshaw (lists)
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=9cffe927-2ac8-ad21-db59-2c3d0f5f3a10@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@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).