git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Di Marco <dmr@ethzero.com>
To: Antoine Pelisse <apelisse@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH] Geolocation support
Date: Thu, 23 May 2013 13:58:20 +0200	[thread overview]
Message-ID: <87r4gx3o2r.fsf@ethzero.com> (raw)
In-Reply-To: <CALWbr2w3=DTAMkFtJoLF1_X46fefpEq2WtTb7HGiTiOExFHG3w@mail.gmail.com> (Antoine Pelisse's message of "Thu, 23 May 2013 11:52:52 +0200")

Antoine Pelisse <apelisse@gmail.com> writes:

   On Thu, May 23, 2013 at 10:45 AM, Ramkumar Ramachandra
   <artagnon@gmail.com> wrote:
   > Alessandro Di Marco wrote:
   >> this is a hack I made a couple of years ago in order to store my current
   >> location in git commits (I travel a lot and being able to associate a
   >> place with the commit date helps me to quickly recover what were doing
   >> at that time). Long story short, the screeenshot at
   >> http://tinypic.com/r/wars40/5 shows the new gitk interface once this
   >> patch has been integrated. Geolocation is controlled by two envvars
   >> GIT_AUTHOR_PLACE and COMMITTER_PLACE, respectively. You can set them via
   >> something like this:
   >
   > Obviously very interesting.  Now, how do we mainline (parts of) this
   > feature?  I'll raise some questions here:

   I think it could be nice to provide a simple shell script to build the
   location, callable from a post-commit hook, to construct a
   "geolocation" note. Gitk could be programmed to read the notes to get
   the location, but once again, I'm not sure it should be mainlined.

Well, I don't see how the file can be kept synchronized with the tree,
but in case it would be also suitable for the author/committer name,
email and date :-)

Seriously, this is just a hack; the other nice thing coming out from
this patch is what I called the Project's Patch Graph (or PPG), ie. a
DAG starting from the project founder location and spreading all over
the world (depending on the project of course!) IMHO it's an interesting
snapshot of how the project is evolving.

  reply	other threads:[~2013-05-23 11:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 13:25 [PATCH] Geolocation support Alessandro Di Marco
2013-05-23  8:45 ` Ramkumar Ramachandra
2013-05-23  9:52   ` Antoine Pelisse
2013-05-23 11:58     ` Alessandro Di Marco [this message]
2013-05-23 17:48     ` Junio C Hamano
2015-02-09  0:03       ` Alessandro Di Marco
2015-02-09  1:24         ` Junio C Hamano
2015-02-09 13:57           ` Ævar Arnfjörð Bjarmason
2015-02-09 19:13             ` Junio C Hamano
2015-02-12 20:50               ` Alessandro Di Marco
2015-02-12 20:57                 ` Junio C Hamano

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=87r4gx3o2r.fsf@ethzero.com \
    --to=dmr@ethzero.com \
    --cc=apelisse@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.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).