From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jay Soffian <jaysoffian@gmail.com>, Miles Bader <miles@gnu.org>,
git@vger.kernel.org
Subject: Re: orthogonal cases of log --date option
Date: Fri, 6 Mar 2009 07:12:58 -0500 [thread overview]
Message-ID: <20090306121258.GC3437@sigill.intra.peff.net> (raw)
In-Reply-To: <7vk573t4cm.fsf@gitster.siamese.dyndns.org>
On Fri, Mar 06, 2009 at 12:58:33AM -0800, Junio C Hamano wrote:
> Jay Soffian <jaysoffian@gmail.com> writes:
>
> > Yeah, that part is easy. I wasn't sure the best way to handle places
> > where a constant date_mode is used e.g.:
> >
> > pp_user_info(NULL, CMIT_FMT_EMAIL, &sb, committer, DATE_RFC2822,
> > encoding);
>
> One approach that will be hated by libgit2 effort would be to keep the
> date_mode an enum as before (sans DATE_LOCAL) and make the "tz_offset"
> thing as a setting global to the process, defined in environ.c
I haven't looked, but might it not be possible to put it in the rev_info
struct next to the date format, but not as part of a struct? You will
then sometimes have to pass two options around (the format and the tz
offset) instead of one (the struct with both), but it makes split usage
much easier:
pp_user_info(NULL, CMIT_FMT_EMAIL, &sb, committer, DATE_RFC2822,
revs->tz_offset, encoding);
-Peff
next prev parent reply other threads:[~2009-03-06 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 8:18 orthogonal cases of log --date option Miles Bader
2009-03-03 8:34 ` Jeff King
2009-03-03 8:45 ` Junio C Hamano
2009-03-05 10:43 ` Jeff King
2009-03-05 21:04 ` Jay Soffian
2009-03-05 21:11 ` Jeff King
2009-03-05 22:21 ` Junio C Hamano
2009-03-06 5:23 ` Jeff King
2009-03-06 6:50 ` Junio C Hamano
2009-03-06 6:58 ` Jay Soffian
2009-03-06 8:02 ` Junio C Hamano
2009-03-06 8:31 ` Jay Soffian
2009-03-06 8:58 ` Junio C Hamano
2009-03-06 12:12 ` Jeff King [this message]
2009-03-06 12:10 ` Jeff King
2009-03-06 12:09 ` Jeff King
2009-03-06 1:47 ` Miles Bader
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=20090306121258.GC3437@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=miles@gnu.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).