On 13/01/2020 13:44, Richard Earnshaw (lists) wrote:
> 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.
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 a
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
On 10/01/2020 14:01, Richard Earnshaw (lists) wrote:
On 10/01/2020 13:29, Richard Biener wrote:
On Fri, Jan 10, 2020 at 2:23 PM 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
cur
On 10/01/2020 13:29, Richard Biener wrote:
On Fri, Jan 10, 2020 at 2:23 PM 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-
On Fri, Jan 10, 2020 at 2:23 PM 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
