From: demerphq <demerphq@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Jeff King <peff@peff.net>, Git <git@vger.kernel.org>
Subject: Re: Gnome chose Git
Date: Thu, 19 Mar 2009 22:59:08 +0100 [thread overview]
Message-ID: <9b18b3110903191459q23af2bf9q998de27feb8dae2a@mail.gmail.com> (raw)
In-Reply-To: <20090319215331.GW23521@spearce.org>
2009/3/19 Shawn O. Pearce <spearce@spearce.org>:
> demerphq <demerphq@gmail.com> wrote:
>> 2009/3/19 Shawn O. Pearce <spearce@spearce.org>:
>> > "Shawn O. Pearce" <spearce@spearce.org> wrote:
>> >
>> > git log -g branch@{now}
>>
>> Ah! Much nicer! Thanks.
>>
>> Is there by any chance any way to set the date format it uses to
>> something more suitable for machine processing?
>
> I don't think so. If you want to machine process it, why not
> just read the reflog directly? Its a really simple format.
Mostly my problem with that is that it violates the abstraction. If i
update git and the reflog format changes my script breaks. I dont
necessarily know where it will be located, etc. And while no doubt i
can reverse engineer the format, well, who knows maybe Ill miss
something important, I mean is it documented anywhere?
So i guess if the format were documented (and thus changing it would
break compatibility and be noted in the changes file) then it would be
fine to do so, but it seems to me making a way to access the reflog
data in a structured way via a plumbing level command makes more
sense. (At the very least this abstract the user of having to figure
out where the log is stored).
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
next prev parent reply other threads:[~2009-03-19 22:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 11:23 Gnome chose Git Teemu Likonen
2009-03-19 11:29 ` Sverre Rabbelier
2009-03-19 11:33 ` Mike Ralphson
2009-03-19 16:29 ` Andreas Ericsson
2009-03-19 13:33 ` Michael J Gruber
[not found] ` <1cd1989b0903190643p19a40718yc4fd2730aab0a9a0@mail.gmail.com>
[not found] ` <49C24D9B.1060301@drmicha.warpmail.net>
2009-03-19 14:01 ` Pat Notz
2009-03-19 15:16 ` Shawn O. Pearce
2009-03-19 15:50 ` Pat Notz
2009-03-19 20:14 ` Jeff King
2009-03-19 21:40 ` demerphq
2009-03-19 21:43 ` Shawn O. Pearce
2009-03-19 21:44 ` Shawn O. Pearce
2009-03-19 21:51 ` demerphq
2009-03-19 21:53 ` Shawn O. Pearce
2009-03-19 21:59 ` demerphq [this message]
2009-03-19 23:17 ` Johannes Schindelin
2009-03-19 21:48 ` demerphq
2009-03-20 5:28 ` Jeff King
2009-03-20 6:00 ` [PATCH] make oneline reflog dates more consistent with multiline format Jeff King
2009-03-20 8:33 ` Gnome chose Git Michael J Gruber
2009-03-20 20:03 ` Jeff King
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=9b18b3110903191459q23af2bf9q998de27feb8dae2a@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).