On 5/26/20 7:14 AM, Martin Liška wrote:
On 5/26/20 3:11 PM, Richard Earnshaw wrote:
On 26/05/2020 14:09, Martin Liška wrote:
On 5/26/20 1:18 PM, Richard Earnshaw wrote:
On 26/05/2020 12:14, Martin Liška wrote:
On 5/26/20 12:23 PM, Richard Earnshaw wrote:
I thought we had a convention that aliases we added were prefixed
with
'gcc-'? This seems to go against that.
You are right, but this one is so handy ;)
What name do you suggest?
Martin
gcc-ci?
What the abbreviation stands for?
Martin
R.
CheckIn
For those who come from the SVN days where ci was the standard
abbreviation for committing :-)
Ah, I see. Anyway, I prefer the original name even though it violates
the naming policy.
Let other express their preferences (Jason?).
Personally I struggle to keep track of all the different command
and function names (e.g., in GCC) and what they do. I find
consistent names and behaviors helpful (and conversely,
inconsistencies trip me up time and time again). So if/since there
is a convention to prefix gcc Git commands with gcc- I would prefer
to use it consistently, even if shorter names might seem nicer or
more convenient. We don't check things in so often that typing
a few extra characters should be a burden.
By the way, it's nice that the existing gcc- aliases are documented
on https://gcc.gnu.org/gitwrite.html. I would suggest to add this
one there as well.
Martin
