From: Wagner Ferenc <wferi@niif.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: bonding sysfs output
Date: Wed, 28 Nov 2007 02:03:44 +0100 [thread overview]
Message-ID: <87oddfji4v.fsf@szonett.ki.iif.hu> (raw)
In-Reply-To: <20071127021418.8a05d225.akpm@linux-foundation.org> (Andrew Morton's message of "Tue, 27 Nov 2007 02:14:18 -0800")
Andrew Morton <akpm@linux-foundation.org> writes:
> On Tue, 27 Nov 2007 10:56:43 +0100 Ferenc Wagner <wferi@niif.hu> wrote:
>
>>> - raise patches against the latest Linus tree
>>> (ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/)
>>
>> I thought it was better to change to git. Isn't it so?
>> SubmittingPatches has nothing to say about that...
>> Can I find collected best practices somewhere? Which tree, which
>> branch, how/when to rebase, format-patch, etc...
>
> gosh. Documentation/Submit*,
> http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt,
> http://linux.yyz.us/patch-format.html, other places. Probably people have
> written books about it by now. But don't sweat it - you're close enough ;)
I wonder where the information got lost... I miss docs on submitting
patches from git ONLY. The general documentation is pretty good and
helpful, just doesn't treat git (not using git in general, but using
it for submitting patches to the Linux kernel). On the other hand
there's a multitude of repositories to clone times a zillion branches
to follow. Which should be the basis of the patches? That's not very
clear.
Anyway, find them in my previous mails. Too bad I realised just after
the fact that cosmetic changes should go first. Hope it's mostly OK.
--
Regards,
Feri.
next prev parent reply other threads:[~2007-11-28 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 15:12 bonding sysfs output Wagner Ferenc
2007-11-26 4:51 ` Andrew Morton
2007-11-26 8:29 ` Wagner Ferenc
2007-11-27 8:44 ` Andrew Morton
2007-11-27 9:56 ` Ferenc Wagner
2007-11-27 10:14 ` Andrew Morton
2007-11-28 1:03 ` Wagner Ferenc [this message]
2007-12-05 22:59 ` Jean Delvare
2007-12-06 10:13 ` Ferenc Wagner
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=87oddfji4v.fsf@szonett.ki.iif.hu \
--to=wferi@niif.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).