X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<20120915111305.22948.qmail@stuge.se>
Date:	Sat, 15 Sep 2012 13:13:05 +0200
From:	Peter Stuge <peter AT stuge DOT se>
To:	gEDA user mailing list <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] [PATCH] fix PostScript headers (was: gschem
	command line printing)
Mail-Followup-To:	gEDA user mailing list <geda-user AT delorie DOT com>
References:	<1310451080 DOT 87097 DOT YahooMailClassic AT web39503 DOT mail DOT mud DOT yahoo DOT com> <ivilg9$qc1$1 AT dough DOT gmane DOT org> <20120915105144 DOT GA19447 AT visitor2 DOT iram DOT es>
MIME-Version:	1.0
In-Reply-To:	<20120915105144.GA19447@visitor2.iram.es>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Gabriel Paubert wrote:
> keyword. Here is the one-liner (actually single character) patch, 
> EndComments needs an uppercase 'C'.
> 
> Could someone please check it in?
> 
> Or should I ask for an account to commit trivial patches like this one?

No matter what the patch is you should always make it available in a
"git friendly" format. There are two common delivery methods for
changes to git repositories, but regardless you must always create an
actual commit in your local repository first. Then, you do one of:

1. git format-patch + email attachment, or git send-email directly
or
2. git push  to somewhere and email the URL to where you pushed to

In all cases make sure that your commit is based on the very latest
state of the repository that you are patching. git pull --rebase is
your friend.


//Peter

- Raw text -