From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: stgit: another way of storing patches
Date: Tue, 20 Nov 2007 09:53:55 -0500 [thread overview]
Message-ID: <9e4733910711200653g4d87c433gae2d48f3508940f5@mail.gmail.com> (raw)
What about storing each stg git patch in a branch and then
auto-merging them into the working copy? That would allow per patch
history and undo. Would it make them easier to share? You could use
tag names to tell stg how to merge and make the working branch.
--
Jon Smirl
jonsmirl@gmail.com
next reply other threads:[~2007-11-20 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 14:53 Jon Smirl [this message]
2007-11-21 11:24 ` stgit: another way of storing patches Karl Hasselström
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=9e4733910711200653g4d87c433gae2d48f3508940f5@mail.gmail.com \
--to=jonsmirl@gmail.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).