It's fair to say that I'm a Git newbie (more familiar with CVS). I now
have the head of my "master" branch, from which I would like to create a
patch. I'm pretty happy with the behavior of the code, and the response
I just got from
git pull git://icarus.com/~steve-icarus/verilog v0_8-branch
made me even happier. That response was "Already up-to-date."
The patch, if committed, would bring the head of Steve Williams's
"v0_8-branch" branch up to agreement with my "master". As suggested in
the Icarus Verilog Developer Guide
<http://iverilog.wikia.com/wiki/Developer_Guide#Submitting_Patches>, I
attempted (with skepticism)
git format-patch '@{1}'
The skepticism came from the fact that "v0_8-branch" is not explicitly
given (nor is the remote repository), although Git may know that
implicitly from the local repository. The result was local creation of
3143 patch files, each apparently describing a past patch on the
"v0_8-branch" branch. If a patch describing the current head difference
was created, I don't know where it went. Also, I don't understand that
second argument to git on the command line above. It must be
[ <since> | <revision range> ]
from the man page
<http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html>.
--
Alan Feldstein
Cosmic Horizon logo
http://www.alanfeldstein.com/
+1 585 415 6682
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
