[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Referring to revisions in the git future.
From: |
Alan Mackenzie |
Subject: |
Re: Referring to revisions in the git future. |
Date: |
Sat, 1 Nov 2014 09:46:04 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Good morning, David.
On Sat, Nov 01, 2014 at 08:49:34AM +0100, David Kastrup wrote:
> It's not like anybody's going to want to type off "abbreviations" by
> hand anyway: too error-prone.
I'm going to want to do this, that's why I started this thread. Using a
computer to kill and yank such a number is going to be such a downer. Do
you also kill and yank a variable name each time you need to type it in,
or do you just type it?
Likely, I'm not going to be able to do this. Remembering and typing in a
revision number is trivial: two chunks of memory - one for the bit that
slowly changes "118" the other for the "220" at the end. With 40 digit
hex strings, even abbreviated, it's going to be 6 or 7 chunks to
memorise. As you say, this will be error-prone.
> Just paste the full thing. Really. I've been developing for years
> with Git, and that's just what everybody does most of the time.
Because they have to, not because it's their preferred way of working.
> --
> David Kastrup
--
Alan Mackenzie (Nuremberg, Germany).
- Re: Referring to revisions in the git future., Tassilo Horn, 2014/11/01
- Re: Referring to revisions in the git future., David Kastrup, 2014/11/01
- Re: Referring to revisions in the git future., Alan Mackenzie, 2014/11/01
- Re: Referring to revisions in the git future., David Kastrup, 2014/11/01
- Re: Referring to revisions in the git future., Alan Mackenzie, 2014/11/01
- Re: Referring to revisions in the git future, Ivan Shmakov, 2014/11/01
- Re: Referring to revisions in the git future, Alan Mackenzie, 2014/11/01