> You should use the latest version of the patch series (v11), because the
> blank line is now automatically added.
Yes interpret-trailers add the blank line, but when call `git commit
-m "$MSG" -e` it isn't displayed.
I think this happens due to the default value of 'cleanup' option of
git-commit
Thanks to all.
With interpret-trailers has been easy to make a simple script, also it
checks if the Hash passed is a valid Object.
I haven't found a simple way to mantain the blank line above the
output of interpet-trailers (not even through cleanup).
Follows the script, maybe could be usefull for
Jeff King wrote:
> [1] I do not know about others, but I typically cut and paste from
> another terminal, and use the following alias in my config:
>
> [alias]
> ll = "!git --no-pager log -1 --pretty='tformat:%h (%s, %ad)'
> --date=short"
I have:
[alias]
short = show --quie
On Mon, Apr 28, 2014 at 08:35:52PM +0200, enzodici...@gmail.com wrote:
> For example, thinking about it, I've imagined to add this feature to `git
> commit`:
>
> git commit --see-also ...
Jonathan mentioned already that we typically just do this by hand[1],
though look on the list for the
Thank you very much
> Why not?
the reason is to avoid mistakes with the hash. An automatic approach
can verify the existence of the commit.
> See the output of
>
> git log --grep='In commit '
>
> and
>
> git log --grep='In v'
I've just tried the commands and noticed that this ca
Hi,
enzodici...@gmail.com wrote:
> Hi to all, I'm trying to figure out what is the best way (and if it
> exists) to link a message of a commit to another commit.
[...]
> Obviously I don't mean to put the raw Hash,
Why not?
See the output of
git log --grep='In commit '
and
git
Hi to all, I'm trying to figure out what is the best way (and if it exists) to
link a message of a commit to another commit.
I start by saying I don't know Git very well so maybe this question can be very
trival for someone but I've googled and searched into the Mailing List with
little success.
7 matches
Mail list logo