On Tue, 11 Nov 2008 16:03:50 -0700, Boyd Lynn Gerber <gerberb@zenez.com> wrote:

quoted text
> Here is a check list I use to make sure my patches are OK.
> 
> http://repo.or.cz/w/git.git?a=blob_plain;f=Documentation/SubmittingPatches;hb=HEAD
> ...
> > I'm by now way offended or scared away if you reject these kind of
             ^
/me meant "no" where he wrote "now" :( :(
I can imagine people interpreting that sentence very very wrong.

quoted text
> > patches
> 
> The crowed here may seem harsh but they really are not.  They just have a 
> lot to do and getting things to them in a format that is easy to follow 
> and uses the above URL guildlines assists them in looking at the patches, 
> commit messages and sign-off.  Git requires a sign-off in order for them 
> to use the patches.  It is a way to make sure everything is kept above 
> board and proper.  This allow ever line of code to have a resource as to 
> where and whence it ...
> 
> Do not give up.  Just try to do things in a manner that is easy to allow 
> your patches into Git.

-- 
H.Merijn Brand          Amsterdam Perl Mongers  http://amsterdam.pm.org/
using & porting perl 5.6.2, 5.8.x, 5.10.x, 5.11.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, SuSE 10.1, 10.2, and 10.3, AIX 5.2, and Cygwin.
http://mirrors.develooper.com/hpux/           http://www.test-smoke.org/
http://qa.perl.org      http://www.goldmark.org/jeff/stupid-disclaimers/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html