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: Commit messages and the move to git


On Wed, Nov 20, 2019 at 08:58:05AM +0000, Jonathan Wakely wrote:
> > Most of the time after I type "git log" I type "/\<123456\>".  We need
> > to keep a way to easily map SVN revision ids to git commits, and
> 
> As a aside, I use these aliases often with the current git-svn repo:
> 
> $ git help srev
> 'srev' is aliased to 'svn log --show-commit --oneline -r'
> $ git srev 276968
> r276968 | aa45db50a03 |         PR c++/91930 - ICE with constrained
> inherited default ctor.

Handy, but:

svn: E155007: '/home/segher/src/gcc' is not a working copy

I won't set up git-svn in my main work space, that would cause all kinds
of problems (not in the least that it encourages accidents) -- it's not
necessarily a great idea to have two-headed monsters in your living room.

> $ git help sshow
> 'sshow' is aliased to '!f(){ git srev ${1#r} | awk -F '|'
> '/^r[[:digit:]]/ {if (length($2)) print $2}' | xargs --no-run-if-empty
> git show ; }; f'
> 
> These won't work once we move to Git though.

It would be good if whatever convention we do for commit messages and
their first line would be machine parseable as well.


Segher


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