From: Jan Veldeman <jan.veldeman@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Catalin Marinas <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] Stgit - patch history / add extra parents
Date: Thu, 25 Aug 2005 09:09:55 +0200 [thread overview]
Message-ID: <20050825070955.GA762@eros.intern.mind.be> (raw)
In-Reply-To: <Pine.LNX.4.63.0508231731370.23242@iabervon.org>
Daniel Barkalow wrote:
[...]
> > The parents which should be visible to the outside, will always be versions
> > of my development tree, which I have previously pushed out. My way of
> > working would become:
> > * make changes, all over the place, using stgit
> > * still make changes (none of these gets tracked, intermittent versions are
> > lost)
> > * having a good day: changes looks good, I want to push this out:
> > * push my tree out
> > * stgit-free (which makes the pushed out commits, the new parents of my
> > stgit patches)
> > * restart from top
>
> I'm not sure how applicable to this situation stgit really is; I see stgit
> as optimized for the case of a patch set which is basically done, where
> you want to keep it applicable to the mainline as the mainline advances.
Maybe I forgot to mention this: I would also like to have my development
tree split up in a patch stack. The separate patches makes tracking the
mainline a lot easier (conflicts are a lot easier to solve)
>
> For your application, I'd just have a git branch full of various stuff,
> and then generate clean commits by branching mainline, diffing development
> against it, cutting the diff down to just what I want to push, and
> applying that. Then the clean patch goes into stgit.
But this would assume that once the patch goes into stgit, it won't
change except when the parent gets updated. I think we will still change
the patches quite a bit and simultanious by a couple of people.
>
> > [...]
> > my proposal does something like this, but a little more: not only does it
> > keep track of the link between old-top and new-top, it also keeps track of
> > the links between old-patch-in-between and new-patch-in-between.
> > (This makes sense when the top is being removed or reordered)
>
> I was thinking of this as being the top and bottom commits for a single
> tracked patch, not as a whole series. I think patches lower wouldn't be
> affected, and patches higher would see this as a rebase.
>
ah, ok, I misunderstood that part
Best regards,
Jan
PS. sorry if my responses are sometimes a bit late, I'm trying to find
more time to spend on this list ;-)
next prev parent reply other threads:[~2005-08-25 7:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 19:57 [RFC] Stgit - patch history / add extra parents Jan Veldeman
2005-08-19 9:53 ` Catalin Marinas
2005-08-19 18:27 ` Jan Veldeman
2005-08-19 22:15 ` Catalin Marinas
2005-08-19 19:48 ` Jan Veldeman
2005-08-20 21:12 ` Catalin Marinas
2005-08-21 9:40 ` Jan Veldeman
2005-08-22 22:10 ` Daniel Barkalow
2005-08-23 16:55 ` Catalin Marinas
2005-08-23 18:05 ` Daniel Barkalow
2005-08-23 21:23 ` Jan Veldeman
2005-08-23 22:23 ` Daniel Barkalow
2005-08-25 7:09 ` Jan Veldeman [this message]
2005-08-25 19:41 ` Daniel Barkalow
2005-08-31 9:27 ` Catalin Marinas
2005-08-31 9:12 ` Catalin Marinas
2005-08-30 21:41 ` Catalin Marinas
2005-08-31 8:59 ` Jan Veldeman
2005-08-31 17:17 ` Daniel Barkalow
2005-08-24 0:23 ` Junio C Hamano
2005-08-24 2:26 ` Linus Torvalds
2005-08-23 1:06 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050825070955.GA762@eros.intern.mind.be \
--to=jan.veldeman@gmail.com \
--cc=barkalow@iabervon.org \
--cc=catalin.marinas@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).