git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@gmail.com>
To: Paul Jackson <pj@sgi.com>
Cc: git@vger.kernel.org
Subject: Re: Stacked GIT 0.1 (a.k.a. quilt for git)
Date: Tue, 28 Jun 2005 11:03:12 +0100	[thread overview]
Message-ID: <tnxwtoeiysf.fsf@arm.com> (raw)
In-Reply-To: <20050624045627.6e9cbaff.pj@sgi.com> (Paul Jackson's message of "Fri, 24 Jun 2005 04:56:27 -0700")

Paul Jackson <pj@sgi.com> wrote:
>> there is no way to modify the log history.
>
> Aha.  If that means what I think it does, then I suspect I will remain
> with quilt.  The per-patch comment is often about the last thing that
> I put in the patch.

OK, you convinced me :-). I will upload a new StGIT version tonight. I
removed the 'commit' command completely. To add changes into the
repository, you would use the 'refresh' command. There is only one git
commit object for each patch and they can be seen with tools like
cg-log on top of the stack base (i.e. the HEAD of the pulled tree).

There is no per-patch history anymore. The patch diff and information
(description, author name etc.) are indefinitely changeable via the
'refresh' command but only one commit with the latest information is
seen in the tree log for each patch.

To pull new changes from the master repository:

   stg pop -a
   cg-udpate (or whatever people use to pull and merge)
   stg push -a

The 'push' command re-bases all the commits corresponding to the StGIT
patches.

Does this make it closer to quilt in functionality?

-- 
Catalin

  parent reply	other threads:[~2005-06-28  9:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 22:44 Stacked GIT 0.1 (a.k.a. quilt for git) Catalin Marinas
2005-06-17 22:10 ` Daniel Barkalow
2005-06-17 22:28   ` Jon Seymour
2005-06-18 21:43     ` Catalin Marinas
2005-06-18 21:35   ` Catalin Marinas
2005-06-19  4:26     ` Daniel Barkalow
2005-06-19  9:24       ` Catalin Marinas
2005-06-24  0:58 ` Paul Jackson
2005-06-24  9:05   ` Catalin Marinas
2005-06-24 10:47     ` Paul Jackson
2005-06-24 11:29       ` Catalin Marinas
2005-06-24 11:56         ` Paul Jackson
2005-06-24 12:27           ` Catalin Marinas
2005-06-28 10:03           ` Catalin Marinas [this message]
2005-06-29 21:28             ` Paul Jackson

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=tnxwtoeiysf.fsf@arm.com \
    --to=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pj@sgi.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).