From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Git Mailinglist" <git@vger.kernel.org>,
"David Symonds" <dsymonds@gmail.com>
Subject: Re: [GitStats] Bling bling or some statistics on the git.git repository
Date: Sat, 12 Jul 2008 00:05:42 +0200 [thread overview]
Message-ID: <bd6139dc0807111505j36c42b6blec299d25d8c0ac9a@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807112252250.8950@racer>
On Fri, Jul 11, 2008 at 11:55 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Fri, 11 Jul 2008, Johannes Schindelin wrote:
>
>> something else I just realized: you might want to use .mailmap, e.g. to
>> coalesce the changes of Shawn "O." Pearce correctly.
>
> Yet another thing: while it is true that git-gui is usually pulled in
> (with the subtree strategy), some parts were changed in git.git directly,
> so you will need to cope with the wholesale rename with every merge.
I think I understand the cause, but I'm not sure I understand the
consequences? Will some files at some times appear to be located at
/path/to/file.txt and at other times at /subdir/path/to/file.txt? If
so, how could I possibly handle that? How do I know that when it says
/path/to/file.txt it means /subdir/path/to/file.txt instead?
> Besides, it is slightly distracting to see the file names differently from
> what they are in HEAD^{tree}. But that may be just me.
Different how? In that it shows the contents of subdirs? For at least
my repo this is a Very Good Thing (tm) as all my source-code is in a
/src directory. If all changes to subdirs were aggregated I wouldn't
get any useful metrics at all. Or am I misunderstanding the difference
between the current output and that of HEAD^{tree}?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-07-11 22:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bd6139dc0807090621n308b0159n92d946c165d3a5dd@mail.gmail.com>
2008-07-11 21:04 ` [GitStats] Bling bling or some statistics on the git.git repository Sverre Rabbelier
2008-07-11 21:22 ` Johannes Schindelin
2008-07-11 21:39 ` Johannes Schindelin
2008-07-11 21:55 ` Johannes Schindelin
2008-07-11 22:05 ` Sverre Rabbelier [this message]
2008-07-11 22:10 ` Johannes Schindelin
2008-07-11 21:55 ` Sverre Rabbelier
2008-07-11 22:11 ` Johannes Schindelin
2008-07-11 22:14 ` Sverre Rabbelier
2008-07-11 23:02 ` Johannes Schindelin
2008-07-11 23:28 ` [PATCH] Add pretty format %aN which gives the author name, respecting .mailmap Johannes Schindelin
2008-07-11 23:30 ` Sverre Rabbelier
2008-07-11 23:42 ` Johannes Schindelin
2008-07-12 8:44 ` Sverre Rabbelier
2008-07-11 21:52 ` [GitStats] Bling bling or some statistics on the git.git repository Sverre Rabbelier
2008-07-11 22:07 ` Johannes Schindelin
2008-07-11 22:50 ` Sverre Rabbelier
2008-07-11 23:33 ` Johannes Schindelin
2008-07-12 7:39 ` Sverre Rabbelier
2008-07-12 22:36 ` Sverre Rabbelier
2008-07-13 0:29 ` Johannes Schindelin
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=bd6139dc0807111505j36c42b6blec299d25d8c0ac9a@mail.gmail.com \
--to=alturin@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=sverre@rabbelier.nl \
/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).