From: Marco Costalba <mcostalba@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git log --pretty=format:%h prints (unrequired) abbreviated sha
Date: Fri, 25 Sep 2009 15:04:15 +0100 [thread overview]
Message-ID: <e5bfff550909250704x724fd4c7lebe7184b4557c7a9@mail.gmail.com> (raw)
In-Reply-To: <e5bfff550909250430x14b0d7f4w5e22467ddd66cc29@mail.gmail.com>
On Fri, Sep 25, 2009 at 12:30, Marco Costalba <mcostalba@gmail.com> wrote:
>
> So I am thinking to some setup somewhere that makes git to use
> abbreviated commits instead of full names. Does exist something like
> this ?
>
Here it is very strange. The problem is that git shell is no more case
sensitive.
I have tried git commit -F ...
and I got error:unkown switch 'f'
So somehow the problem is that all the commands are lowercased, and
this explains why pretty format %H is interpreted as %h so that sha
abbreviated form is used.
Now the question is: how to restore normal case sensitive command parsing ?
Thanks
Marco
P.S: Please, at least answer this last question ;-)
next prev parent reply other threads:[~2009-09-25 14:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 9:40 git log --pretty=format:%h prints (unrequired) abbreviated sha Marco Costalba
2009-09-25 9:46 ` Marco Costalba
2009-09-25 10:33 ` Johannes Sixt
2009-09-25 10:44 ` Marco Costalba
2009-09-25 11:30 ` Marco Costalba
2009-09-25 14:04 ` Marco Costalba [this message]
2009-09-25 14:12 ` Johannes Sixt
2009-09-25 14:18 ` Marco Costalba
2009-09-25 15:27 ` Johannes Sixt
2009-09-25 18:25 ` Marco Costalba
2009-09-25 18:40 ` alexandrul
2009-09-25 18:44 ` Marco Costalba
2009-09-25 19:08 ` Marco Costalba
2009-09-25 19:18 ` alexandrul
2009-09-25 20:04 ` Marco Costalba
[not found] ` <23e749600909251507m345ab66aq74730d1ada75cb7b@mail.gmail.com>
[not found] ` <e5bfff550909260217l7f6e8766te072decee1bbbbf3@mail.gmail.com>
[not found] ` <4ABDE6FF.2090008@gmail.com>
[not found] ` <e5bfff550909260309x1ef007a0k8a1ab85f78fe5c5e@mail.gmail.com>
[not found] ` <23e749600909260500i5e04864bsc845b9f20a11141@mail.gmail.com>
[not found] ` <e5bfff550909260553v38243faaic53860d20322232d@mail.gmail.com>
[not found] ` <e5bfff550909260858u71df1487va569262fc9819415@mail.gmail.com>
[not found] ` <23e749600909261128v4e398dadhc8be096f2500b17e@mail.gmail.com>
2009-09-26 21:55 ` Marco Costalba
2009-09-27 10:40 ` alexandrul
2009-09-25 14:41 ` alexandrul
2009-09-25 15:13 ` Marco Costalba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5bfff550909250704x724fd4c7lebe7184b4557c7a9@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).