From: David Miller <davem@davemloft.net>
To: per.liden@ericsson.com
Cc: netdev@vger.kernel.org
Subject: Re: [GIT PATCH] TIPC updates
Date: Tue, 20 Jun 2006 14:28:13 -0700 (PDT) [thread overview]
Message-ID: <20060620.142813.74565140.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0606201637050.29502@ulinpc219.uab.ericsson.se>
From: Per Liden <per.liden@ericsson.com>
Date: Tue, 20 Jun 2006 16:48:54 +0200 (CEST)
> Please pull from:
>
> git://tipc.cslab.ericsson.net/pub/git/tipc.git
Hi Per.
I agree with James, you should post the patches so that people
can review them.
But not all in one posting! :-)
Look at how other contributors submit their work. They make a set of
postings to the list, one for each patch, and each posting has
a subject that begins with something like "[PATCH 1/N] " where
the "1" increases for each patch and the "N" is the total number
of patches you are submitting for review.
People typically also give an initial "[PATCH 0/N] " posting
where the location of the GIT tree containing the patches lives
and also a general summary of what the upcoming set of patches
do.
There are automated scripts which can take a GIT tree and a given
range of changesets and prebuild the list postings for you. So
the amount of work you need to do for this is minimal.
For example, "git format-patch" and "git send-email" can help you a
lot here.
Thanks!
prev parent reply other threads:[~2006-06-20 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 14:48 [GIT PATCH] TIPC updates Per Liden
2006-06-20 21:28 ` David Miller [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=20060620.142813.74565140.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=per.liden@ericsson.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