On 07/04/2013 08:32 AM, Karl Wiberg wrote:
On Thu, Jul 4, 2013 at 8:09 AM, Gerlando Falauto
<[email protected]> wrote:
I would also add the Cc: tags to that cover letter itself,
Yes.
along with changelog information (i.e. changes wrt to the previous
patch series version, when it is more convenient to document that on
a global basis within the cover letter).
Is that a changelog that you (the human) writes manually, as part of
the cover letter text?
Yes. I would add on top a few "Changes from v2:" lines just to
illustrate how I made use of the feedback.
Sometimes it takes a few weeks before I get some feedback, so I'd rather
have this stored in a safe place than on my hard drive or inbox.
As for the per-patch changelog, it just occurred to me that adding a
"---" line in the commit message already does the trick. Whatever
follows that line is stored within the commit message and spurted
out by git-format-patch, but not applied by git-am. Perhaps that
was so obvious and it is so common practice that no one ever cared
to point it out to me. :-)
I think at least "stg squash" will drop everything after the first
"---\n". But the workflow you suggest seems very reasonable, so if you
find that certain parts of stg makes it awkward, feel free to report
back (or propose a patch!).
OK, sure will!
Adding some kind of "Patch-version: <v>" tag to the cover-letter
would just complete the picture (so that we get a [PATCH v 00/xx]
subject prefix).
Yes.
BTW, is there a way to duplicate a branch managed by stgit? So that
whenever I need to rework something, I can still keep the old
history around? I was thinking of some: NUM=`stg series | wc -l`;
git checkout -b <new>; stg uncommit -n $NUM but perhaps I'm
completely off track here.
"stg reset X" will reset the entire patch stack state to what it was
at commit X *of the .stgit metadata branch*. So for example, if your
branch is master,
$ git tag smurf master.stgit
will snapshot the state, and
$ stg reset smurf
retores it. (Restoring will overwrite the existing patch stack state
on the current branch, but you don't have to do it in the same branch
where you captured the snapshot.)
I think I understand but I'm not that familiar with stg yet.
Last question: is there a way to get "gitk --all" to hide stgit metadata?
Thanks again!
Gerlando
_______________________________________________
stgit-users mailing list
[email protected]
https://mail.gna.org/listinfo/stgit-users
