From: David Greaves <david@dgreaves.com>
To: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] git-tar-tree: small doc update
Date: Fri, 27 May 2005 22:32:51 +0100 [thread overview]
Message-ID: <42979203.7030703@dgreaves.com> (raw)
In-Reply-To: <20050527212032.GB17478@lsrfire.ath.cx>
Rene Scharfe wrote:
>I'll take the blame for
>that contraption, if you don't mind. ;)
>
<snip>
>Author
> ------
>-Written by Linus Torvalds <torvalds@osdl.org>
>+Written by Rene Scharfe.
>
>
Good - this was what I intended to have happen all along :)
Also Junio suggested a more general attribution - which I have now put
into eg git-mkdelta.txt
Git is written by Linus Torvalds <torvalds@osdl.org> and the git-list
<git@vger.kernel.org>.
I'll generalise the rest of the files at some point and respect any more
specific atributions.
David
--
prev parent reply other threads:[~2005-05-27 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 21:20 [PATCH] git-tar-tree: small doc update Rene Scharfe
2005-05-27 21:32 ` David Greaves [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42979203.7030703@dgreaves.com \
--to=david@dgreaves.com \
--cc=git@vger.kernel.org \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=torvalds@osdl.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).