From: "Philip Oakley"
From: "Junio C Hamano"
"Philip Oakley" writes:
I think the
use of "commit" in an angle-bracket-pair in the label for the
section, i.e. "--fixup=", has been considered to be clear
enough to tell that you can use usual extended SHA-1 syntax to
specify the commit you want
From: "Junio C Hamano"
"Philip Oakley" writes:
I think the
use of "commit" in an angle-bracket-pair in the label for the
section, i.e. "--fixup=", has been considered to be clear
enough to tell that you can use usual extended SHA-1 syntax to
specify the commit you want to talk about,
I cert
"Philip Oakley" writes:
>> I think the
>> use of "commit" in an angle-bracket-pair in the label for the
>> section, i.e. "--fixup=", has been considered to be clear
>> enough to tell that you can use usual extended SHA-1 syntax to
>> specify the commit you want to talk about,
>
> I certainly hadn
From: "Junio C Hamano"
Philip Oakley writes:
Be clearer that the --fixup/--squash options can take any of the
gitrevisions methods of specifying a commit, not just a 'hash'.
Signed-off-by: Philip Oakley
---
...
@@ -81,15 +81,15 @@ OPTIONS
--fixup=::
Construct a commit message for use with
Philip Oakley writes:
> Be clearer that the --fixup/--squash options can take any of the
> gitrevisions methods of specifying a commit, not just a 'hash'.
>
> Signed-off-by: Philip Oakley
> ---
> ...
> @@ -81,15 +81,15 @@ OPTIONS
> --fixup=::
> Construct a commit message for use with `reba
Be clearer that the --fixup/--squash options can take any of the
gitrevisions methods of specifying a commit, not just a 'hash'.
Signed-off-by: Philip Oakley
---
v1
It's not immediately obvious what different forms the
option can take. Spell out, and refer to the git revisions guide,
that any of
6 matches
Mail list logo