git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kris Shannon <kris@shannon.id.au>
To: Kjetil Barvik <barvik@broadpark.no>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 0/2] git checkout: one bugfix and one cosmetic change
Date: Tue, 17 Mar 2009 15:56:12 +1100	[thread overview]
Message-ID: <e51f4f550903162156i64b64900g815ee8317720f1a0@mail.gmail.com> (raw)
In-Reply-To: <cover.1237115791.git.barvik@broadpark.no>

2009/3/15 Kjetil Barvik <barvik@broadpark.no>:
> Just one small bugfix patch, and one small cosmetic change.
>
> By the way, I wonder how often the list of 'Primary Authors' and
> 'Contributors' on the webpage http://git-scm.com/about is updated.
> Should'nt it be updated when a new release, like v1.6.2, is made?
>

I was rather surprised to see my name on that list.  A quick git log
showed my one contribution to git-parse-remote way pack in
August 2005.

I'd forgotten about that and was feeling all warm and fuzzy until I did:
git log -- git-parse-remote

and saw that it was deleted a week later :(

  parent reply	other threads:[~2009-03-17  4:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 11:38 [PATCH 0/2] git checkout: one bugfix and one cosmetic change Kjetil Barvik
2009-03-15 11:38 ` [PATCH 1/2] checkout bugfix: use stat.mtime instead of stat.ctime in two places Kjetil Barvik
2009-03-15 11:38 ` [PATCH 2/2] make the ST_{C,M}TIME_NSEC macros more function like Kjetil Barvik
2009-03-15 20:01   ` Junio C Hamano
2009-03-15 21:59     ` Kjetil Barvik
2009-03-16  7:12       ` Junio C Hamano
2009-03-17 17:38         ` Kjetil Barvik
2009-03-15 18:21 ` [PATCH 0/2] git checkout: one bugfix and one cosmetic change Junio C Hamano
2009-03-15 19:38   ` Junio C Hamano
2009-03-16 16:12 ` Michael J Gruber
2009-03-17  4:56 ` Kris Shannon [this message]
2009-03-17  8:43   ` Jeff King
2009-03-17 13:39     ` Michael J Gruber

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=e51f4f550903162156i64b64900g815ee8317720f1a0@mail.gmail.com \
    --to=kris@shannon.id.au \
    --cc=barvik@broadpark.no \
    --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).