From: Marc Singer <elf@buici.com>
To: git@vger.kernel.org
Subject: Converting commits to patch files? HEAD vs HEAD^
Date: Fri, 8 Jul 2005 18:38:59 -0700 [thread overview]
Message-ID: <20050709013859.GA11947@buici.com> (raw)
Jeff Garzik's guide doesn't appear to explain how to get patches back
out of the system.
I've successfully commited a set of changes.
# git diff HEAD^ HEAD
This command will produce a diff of the changes I've made. What is
the HEAD^? Does it refer to the commit before the last one made?
If I've made several commits, I'd like to be able to gather several
together and produce a patch file. Better still, I'd like to be able
to pick a set of discontiguous commits an bundle them into a single
patch. Ought I be using tags?
Finally, given that the upstream repository is git, what is the way to
push commits upstream?
next reply other threads:[~2005-07-09 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 1:38 Marc Singer [this message]
2005-07-09 1:52 ` Converting commits to patch files? HEAD vs HEAD^ Linus Torvalds
2005-07-09 2:41 ` Junio C Hamano
2005-07-09 11:10 ` Catalin Marinas
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=20050709013859.GA11947@buici.com \
--to=elf@buici.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).