From: Jason Earl <jearl@notengoamigos.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: magit + git + authorship
Date: Sun, 10 Mar 2013 20:20:08 -0600 [thread overview]
Message-ID: <87ip4ysmnb.fsf@notengoamigos.org> (raw)
In-Reply-To: <87fw02svu5.fsf@pobox.com> (Andy Wingo's message of "Mon, 11 Mar 2013 00:01:38 +0100")
On Sun, Mar 10 2013, Andy Wingo wrote:
> Hi!
>
> In something of an embarassment, I mistakently attributed to Jason Earl
> a number of commits:
>
> b5870f25 * origin/stable-2.0 stable-2.0 rely on gnulib for `poll'
> 428f9e95 * import `poll' from gnulib
> 988ca6b2 * add %site-ccache-dir
> a4b4fbbd * excise use of "iff" in the manual
> e9381f58 * fix AC_CHECK_DECLS for `alarm'
> cfe24bc4 * use chmod portably in (system base compile)
On the one hand I am very sorry that this happened. On the other, I
have to admit that was my best git pull ever!
> 84dfde82 is correctly attributed.
I would say that is being very generous. I did learn a lot though. I
also have to say that I have never had so much fun filing a bug. Guile
has a very nice community.
Thanks,
Jason Earl
prev parent reply other threads:[~2013-03-11 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 23:01 magit + git + authorship Andy Wingo
2013-03-11 2:20 ` Jason Earl [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ip4ysmnb.fsf@notengoamigos.org \
--to=jearl@notengoamigos.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).