From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Joe Corneli <holtzermann17@gmail.com>
Cc: "Love Hörnquist Åstrand" <lha@kth.se>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Michael Haggerty" <mhagger@alum.mit.edu>
Subject: Re: [PATCH] Optionally parse author information
Date: Sun, 16 Jan 2011 09:02:57 +0530 [thread overview]
Message-ID: <20110116033253.GA22707@kytes> (raw)
In-Reply-To: <AANLkTi=ddJYT8YiUDYy80xobkxJnvuREN-09=464P_vB@mail.gmail.com>
Hi Joe,
Joe Corneli writes:
> I tested it, and it seems to use email handle instead of author name
> (perhaps that's intentional, though in my case it's not so desirable)
> but, quite critically, it gets the dates wrong:
Yes. I didn't change it's core behavior- it used to extract the
information from the committer's email address previously; I just
changed it to use the author's email address. For dates, it uses
committer dates again, and this is probably desirable: author dates
aren't necessarily monotonic, and this can break some functionality in
SVN.
Ofcourse, a lot more is possible with an patch that allows users to
configure all these things. Until then, I recommend that you just edit
the source to achieve the desired results.
-- Ram
prev parent reply other threads:[~2011-01-16 3:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 1:27 working with a large repository and git svn Joe Corneli
2011-01-12 15:30 ` Wesley J. Landaker
2011-01-13 0:54 ` Joe Corneli
2011-01-13 3:23 ` Jonathan Nieder
2011-01-14 7:43 ` Joe Corneli
2011-01-14 8:05 ` Ramkumar Ramachandra
2011-01-14 8:29 ` Jonathan Nieder
2011-01-14 9:23 ` Michael Haggerty
[not found] ` <F0299861-B36C-459C-972E-856212A92615@kth.se>
2011-01-14 10:16 ` [PATCH] Optionally parse author information Ramkumar Ramachandra
2011-01-16 2:17 ` Joe Corneli
2011-01-16 2:57 ` Jonathan Nieder
2011-01-16 3:32 ` Ramkumar Ramachandra [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=20110116033253.GA22707@kytes \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=holtzermann17@gmail.com \
--cc=jrnieder@gmail.com \
--cc=lha@kth.se \
--cc=mhagger@alum.mit.edu \
/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).