From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Shawn Pearce <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: t8001-annotate.sh fails on Mac OS X
Date: Fri, 26 May 2006 18:40:38 -0700 [thread overview]
Message-ID: <20060527014037.GA11935@h4x0r5.com> (raw)
In-Reply-To: <7vpsi1qyi2.fsf@assigned-by-dhcp.cox.net>
On Thu, May 25, 2006 at 08:02:45PM -0700, Junio C Hamano wrote:
> Shawn Pearce <spearce@spearce.org> writes:
>
> > I think we had hoped that one of the two tools would prove to be
> > _the_ annotation/blame tool and would get used but thus far that
> > hasn't happened.
>
> I've been taking this as an indication that annotate/blame does
> not actually matter in the real world.
It probably doesn't matter in the real world.
At the moment, I'd blame annotate for being wrong, I know it does the
wrong thing on some merges, and I had a plan to try to fix it, but I got
distracted by finding a new job and moving across the country, so I
haven't really had a chance to fix it, something to look at shortly, I
hope. (I'm having problems getting one of my machines back up, so
that's going to slow me down slightly)
> Or git is not yet used in the real world. Or perhaps a bit of
> both.
It's just that "annotate" isn't a common operation in the communities
that Git has made it into.
next prev parent reply other threads:[~2006-05-27 1:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 23:53 t8001-annotate.sh fails on Mac OS X Stefan Pfetzing
2006-05-26 1:11 ` Shawn Pearce
2006-05-26 3:02 ` Junio C Hamano
2006-05-26 3:12 ` Martin Langhoff
2006-05-27 1:40 ` Ryan Anderson [this message]
2006-05-26 4:32 ` Fredrik Kuivinen
2006-05-26 13:36 ` Johannes Schindelin
2006-05-26 13:51 ` Stefan Pfetzing
2006-05-27 18:13 ` Nicolas Vilz 'niv'
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=20060527014037.GA11935@h4x0r5.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.org \
/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).