From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Auke Kok" <auke-jan.h.kok@intel.com>
Cc: git@vger.kernel.org
Subject: Re: stgit: cannot push a patch - Python trace dump
Date: Fri, 15 Sep 2006 15:33:37 +0100 [thread overview]
Message-ID: <b0943d9e0609150733v6cbe465esfd8d2b598c496768@mail.gmail.com> (raw)
In-Reply-To: <450AB81F.2090305@intel.com>
On 15/09/06, Auke Kok <auke-jan.h.kok@intel.com> wrote:
> Catalin Marinas wrote:
> > Thanks, I fixed StGIT to cope with this and I'll update the repository
> > and snapshot tonight (which, BTW, will contain the initial support for
> > patch history tracking).
>
> awesome and awesome, allthough I have no idea what that (patch history
> tracking) is about :)
It keeps the history of all the patch modifications (like refresh,
push) so that you can get previous versions if something went wrong.
It's like having many small commits reflecting the changes to a patch.
These commits are totally separate from the main patch commit (so that
an StGIT repository is still compatible with GIT) but you can access
them with "stg log [--graphical] <patch>". The --graphical option will
automatically invoke gitk.
--
Catalin
prev parent reply other threads:[~2006-09-15 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 5:07 stgit: cannot push a patch - Python trace dump Auke Kok
2006-09-15 8:58 ` Catalin Marinas
2006-09-15 14:26 ` Auke Kok
2006-09-15 14:33 ` Catalin Marinas [this message]
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=b0943d9e0609150733v6cbe465esfd8d2b598c496768@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=auke-jan.h.kok@intel.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).