git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: "git discussion list" <git@vger.kernel.org>,
	"Andy Parkins" <andyparkins@gmail.com>,
	"Sitaram Chamarty" <sitaramc@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Marc Branchaud" <mbranchaud@xiplink.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Chris Hiestand" <chiestand@salk.edu>
Subject: Re: [RFC v2] git-multimail: a replacement for post-receive-email
Date: Sat, 09 Mar 2013 06:32:32 +0100	[thread overview]
Message-ID: <513AC970.6030502@alum.mit.edu> (raw)
In-Reply-To: <512B4203.3090802@alum.mit.edu>

On 02/25/2013 11:50 AM, Michael Haggerty wrote:
> On 02/25/2013 10:54 AM, Matthieu Moy wrote:
>> [...] Works for me. One minor knit: you've included 10-characters sha1s (this
>> comes from
>>
>>         self.short = read_output(['git', 'rev-parse', '--short=10', sha1])
>>
>> ), I'd find it better with shorter sha1s. In the case of branch update,
>> if the branch name is a bit long, it could be nice to save a few
>> characters.
>>
>> Why not just say "git rev-parse --short", without argument? This way,
>> the default is used, ie. AFAICT it uses 7 characters by default, but
>> will use more if needed to keep the unicity.
> 
> [...] I guess I will change the code to use $(git rev-parse --short) (i.e.,
> shorter SHA1s) but reserving 10 columns in tables for them (which can be
> done via Python string formatting in the templates).  That should give
> the best of both worlds.

I implemented this change (allow git to choose the SHA1 abbreviation
length) and just pushed it to github.

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  reply	other threads:[~2013-03-09  5:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27  8:37 [RFC v2] git-multimail: a replacement for post-receive-email Michael Haggerty
2013-01-29 15:25 ` Ævar Arnfjörð Bjarmason
2013-01-30  2:27   ` Chris Hiestand
2013-02-13 14:56 ` Matthieu Moy
2013-02-13 15:26   ` Andy Parkins
2013-02-13 16:12     ` Matthieu Moy
2013-02-13 21:42   ` Michael Haggerty
2013-02-14 12:55     ` Matthieu Moy
2013-02-15  5:07       ` Michael Haggerty
2013-02-20 12:28 ` Matthieu Moy
2013-02-24  5:31   ` Michael Haggerty
2013-02-25  9:54     ` Matthieu Moy
2013-02-25 10:50       ` Michael Haggerty
2013-03-09  5:32         ` Michael Haggerty [this message]
2013-02-24  5:53   ` Michael Haggerty
2013-02-25 10:01     ` Matthieu Moy
2013-03-04  8:56   ` Matthieu Moy

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=513AC970.6030502@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=andyparkins@gmail.com \
    --cc=avarab@gmail.com \
    --cc=chiestand@salk.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mbranchaud@xiplink.com \
    --cc=sitaramc@gmail.com \
    /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.
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 NNTP newsgroup(s).