From: Luben Tuikov <ltuikov@yahoo.com>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Remove redundant "commit" link from shortlog
Date: Fri, 6 Oct 2006 11:27:20 -0700 (PDT) [thread overview]
Message-ID: <20061006182720.88733.qmail@web31812.mail.mud.yahoo.com> (raw)
In-Reply-To: <20061006135508.GO20017@pasky.or.cz>
--- Petr Baudis <pasky@suse.cz> wrote:
> Dear diary, on Fri, Sep 29, 2006 at 01:48:40AM CEST, I got a letter
> where Luben Tuikov <ltuikov@yahoo.com> said that...
> > Remove the redundant "commit" link from shortlog.
> > It can be had by simply clicking on the entry title
> > of the row.
> >
> > Signed-off-by: Luben Tuikov <ltuikov@yahoo.com>
>
> And what if the commit message is empty?
>
> Witness at http://repo.or.cz/?p=test;a=summary
Clearly a pathological case. Who or why would anyone do this?
I don't think we should worry about such pathological cases.
Commits without commit messages do not question GIT. They
question the committer... (that's the morning chuckle)
Luben
>
> --
> Petr "Pasky" Baudis
> Stuff: http://pasky.or.cz/
> #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
> $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
> lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2006-10-06 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 23:48 [PATCH] gitweb: Remove redundant "commit" link from shortlog Luben Tuikov
2006-10-06 13:55 ` Petr Baudis
2006-10-06 15:08 ` Jakub Narebski
2006-10-06 16:55 ` [PATCH] gitweb: Handle commits with empty commit messages more reasonably Petr Baudis
2006-10-06 18:27 ` Luben Tuikov [this message]
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=20061006182720.88733.qmail@web31812.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).