git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Koch <thomas@koch.ro>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org, vcs-pkg-discuss@lists.alioth.debian.org
Subject: Re: rethinking patch management with GIT / topgit
Date: Mon, 22 Mar 2010 08:59:40 +0100	[thread overview]
Message-ID: <201003220859.41820.thomas@koch.ro> (raw)
In-Reply-To: <20100321203626.GE3533@machine.or.cz>

Hi Petr,

Petr Baudis:
> On Sat, Mar 20, 2010 at 07:53:34PM +0100, Thomas Koch wrote:
> > Petr Baudis:
> >   - tg recreate <patchset> <newbase> <new patchset name>
> >     Creates a new patchset with root <newbase> by creating new patch
> > branches for each patch branch in <patchset>
> >     This command is useful if you need to keep the old patchset to
> > maintain an older version of your Debian package.
> 
> This means wiping out history again; in TopGit, you would ideally
> checkpoint all the branches within the patchset, then just tg update
> your branches. It's another matter that the former is now difficult to
> do easily.
It's not necessary to lose history. Creating a new patchset from a given 
patchset could be done in at least three different ways. Given that you've a 
patchset named patches-x.y.z/* and you'd like to create patches-x.y.z+1/* from 
this, you could

- checkout new patch branches from the top of the old patch branches and merge 
upstream into each of them

- recreate (like rebase) the full history of the patch branches on top of the 
new upstream

- collapse the branch history and create one commit per patch branch on top of 
the new upstream

In all three cases you're free to either keep or throw away the old patchset.

Best regards,

Thomas Koch, http://www.koch.ro

  reply	other threads:[~2010-03-22  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20 17:02 rethinking patch management with GIT / topgit Thomas Koch
2010-03-20 17:47 ` Petr Baudis
2010-03-20 18:53   ` Thomas Koch
     [not found]     ` <201003201953.34666.thomas-5j3myg3OO4w@public.gmane.org>
2010-03-21 20:36       ` Petr Baudis
2010-03-22  7:59         ` Thomas Koch [this message]
2010-03-22 19:30           ` Petr Baudis
2010-03-23  8:09             ` Thomas Koch

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=201003220859.41820.thomas@koch.ro \
    --to=thomas@koch.ro \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=vcs-pkg-discuss@lists.alioth.debian.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).