From: "Gustav Hållberg" <gustav@gmail.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: "David Kågedal" <davidk@lysator.liu.se>,
kha@treskal.com, git@vger.kernel.org
Subject: [PATCH 0/2] Setting git tree of a patch (improved version)
Date: Mon, 24 May 2010 20:52:09 +0200 [thread overview]
Message-ID: <20100524184908.30884.65042.stgit@sambuntu> (raw)
In-Reply-To: <AANLkTimIxtmaUNxp-LNy_ui5__BEBetcjTYE17ygIXD2@mail.gmail.com>
I solved (I think) how to accept (and verify the correctness of) a
tree-ish as argument for 'edit --set-tree'. The first patch in the
series adds support to Repository.rev_parse() for doing that.
The main (the second) is essentially the same as before.
I moved the --set-tree option to be last in the list of options,
making it even more obscure-looking.
---
Gustav Hållberg (2):
Repository.rev_parse: support commits, trees, and blobs
edit: Allow setting git tree of a patch
stgit/commands/edit.py | 39 ++++++++++++++++++++++++++++-----------
stgit/lib/git.py | 10 ++++++----
t/t3300-edit.sh | 15 +++++++++++++++
3 files changed, 49 insertions(+), 15 deletions(-)
--
next prev parent reply other threads:[~2010-05-24 18:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 17:33 [StGit PATCH] edit: Allow setting git tree SHA1 of a patch Gustav Hållberg
2010-05-17 17:14 ` Karl Wiberg
2010-05-21 12:37 ` Catalin Marinas
2010-05-21 13:59 ` David Kågedal
2010-05-21 15:16 ` Catalin Marinas
2010-05-21 15:29 ` David Kågedal
2010-05-21 15:32 ` Gustav Hållberg
2010-05-21 15:58 ` Catalin Marinas
2010-05-21 17:48 ` David Kågedal
2010-05-21 18:45 ` Gustav Hållberg
2010-05-24 18:52 ` Gustav Hållberg [this message]
2010-05-24 18:52 ` [PATCH 1/2] Repository.rev_parse: support commits, trees, and blobs Gustav Hållberg
2010-05-24 18:52 ` [PATCH 2/2] edit: Allow setting git tree of a patch Gustav Hållberg
2010-05-25 12:26 ` [PATCH 0/2] Setting git tree of a patch (improved version) Catalin Marinas
2010-05-26 15:34 ` Gustav Hållberg
2010-05-26 21:18 ` 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=20100524184908.30884.65042.stgit@sambuntu \
--to=gustav@gmail.com \
--cc=catalin.marinas@gmail.com \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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).