From: "Lars Hjemli" <hjemli@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>
Subject: A message from the human patch-queue
Date: Sat, 6 Oct 2007 19:18:34 +0200 [thread overview]
Message-ID: <8c5c35580710061018m43f8ceaag9341ee95d39500f5@mail.gmail.com> (raw)
Hi
I've been collecting patches from the list for the last couple of days
and published them as topic-branches on http://hjemli.net/git/git (see
http://article.gmane.org/gmane.comp.version-control.git/60023 if you
wonder _why_ I've done this ;-)
All topic-branches are prefixed with 'q/' and the authors initials,
they're all based on current master
(58ba4f6ac828606fc206cfd5cec412a6974c91a1), and I've run 'make test'
successfully on all topics with code changes. There is also a list of
topics with links to the relevant postings at
http://hjemli.net/git/git/tree/branches?h=q/meta
Please let me know if I've your patches are missing, and I'll swiftly add them.
--
larsh
next reply other threads:[~2007-10-06 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 17:18 Lars Hjemli [this message]
2007-10-06 20:04 ` A message from the human patch-queue Frank Lichtenheld
2007-10-06 20:17 ` Lars Hjemli
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=8c5c35580710061018m43f8ceaag9341ee95d39500f5@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@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 NNTP newsgroup(s).