From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: My sparse repository
Date: Sun, 28 Dec 2008 21:36:49 +0300 [thread overview]
Message-ID: <f19298770812281036u59ac3ecdi2ffbdbe403cdf58d@mail.gmail.com> (raw)
In-Reply-To: <70318cbf0812251716i34608594kaeb537537e28c82f@mail.gmail.com>
On Fri, Dec 26, 2008 at 04:16, Christopher Li <sparse@chrisli.org> wrote:
> On Thu, Dec 25, 2008 at 12:26 PM, Alexey Zaytsev
> <alexey.zaytsev@gmail.com> wrote:
>> Is there a way to look at it in the gitweb? And also, could you please
>
> Good idea. I will ask the kernel.org administrators to add my tree.
>
>> create an experimental branch, for stuff that is not broken and ugly, but
>> needs more discussion? Otherwise I could do this, just didn't want to
>> duplicate the effort.
>
> Sure, what patch do you have in mind?
Like, your makefile cleanups, or the instruction type patch, or
just any random patch you or anyone else happens to write.
It's not hard to pick up patches from the ml, but setting
up a git remote and cheri-picking stuff is easier anyway.
prev parent reply other threads:[~2008-12-28 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 12:17 My sparse repository Christopher Li
2008-12-25 20:26 ` Alexey Zaytsev
2008-12-26 1:16 ` Christopher Li
2008-12-28 18:36 ` Alexey Zaytsev [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=f19298770812281036u59ac3ecdi2ffbdbe403cdf58d@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).