From: Bill Davidsen <davidsen@tmr.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13 git snapshot patches still empty
Date: Fri, 02 Sep 2005 09:59:43 -0400 [thread overview]
Message-ID: <43185ACF.5060401@tmr.com> (raw)
In-Reply-To: <20050901225956.185572ae.akpm@osdl.org>
Andrew Morton wrote:
> Sid Boyce <sboyce@blueyonder.co.uk> wrote:
>
>>For both -git1.gz/.bz2 and -git2.gz/.bz2.
>
>
> http://www.zip.com.au/~akpm/linux/patches/stuff/linus.patch.gz is updated
> once or twice daily. It's Linus's latest tip-of-tree.
That's nice, but consider trying to find bugs when someone reports a
problem and there's no ggod way to tell exactly what patches are
present. At least with git patches, anyone can **easily** replicate the
source tree for debugging.
Is it really that hard to fix the process?
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2005-09-02 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 1:19 2.6.13 git snapshot patches still empty Sid Boyce
2005-09-02 3:17 ` Randy.Dunlap
2005-09-02 3:24 ` Randy.Dunlap
2005-09-02 5:59 ` Andrew Morton
2005-09-02 6:57 ` Sid Boyce
2005-09-02 13:59 ` Bill Davidsen [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=43185ACF.5060401@tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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