Alan M. Feldstein wrote:
> 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>.
Well, I would have guessed it would work because your local git
directory knows that the v0_8-branch is your corrent branch.
What the '@{1}' is supposed to say is "only for the previous commit."
I too am a little weak on this, so I would be glad if one of the
git masters on this list were to come to our rescue here. The
instructions above certainly work for the main trunk, so I would
have thought it would work for your branch as well. I'm at a loss.
Perhaps you have a version issue?
--
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
