From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Incremental patches available
Date: Mon, 26 Jul 2004 18:43:30 +0200 [thread overview]
Message-ID: <200407261707.49889.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040725001114.GA13469@ccure.user-mode-linux.org>
Well, just perfect! I'm very happy about this... Would you please to put there
the splitout version of the patches beyond 2.4.24-1 (the one I already
built and posted)?
Also, maybe you should add a -v# to the end of the name (since if a patch is
buggy, you will maybe create a new version); you may prefer to add
patchname-fix containing the changes, as Andrew Morton does, but in this case
probably it is not very useful (it's easier than popping tons of patches and
modifying one, especially if the fix comes from somebody else, but this is
not our case).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-07-26 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 0:11 [uml-devel] Incremental patches available Jeff Dike
2004-07-26 16:43 ` BlaisorBlade [this message]
2004-07-26 19:54 ` Jeff Dike
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=200407261707.49889.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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