public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: Keeping up to date with the upstream
Date: Mon, 05 Jul 2010 21:37:37 +0000	[thread overview]
Message-ID: <201007052337.37575.PeterHuewe@gmx.de> (raw)
In-Reply-To: <1278362590.5396.35.camel@dermezel>

Am Montag 05 Juli 2010 23:11:22 schrieben Sie:
> So if I understand you correctly should finish my patching first on my
> current branch then checkout master and git reset --hard origin and do
> clean up then go on with something else as obviously those patches will
> not be in and the work I have done is now the patch.
> 
> And then from now on just make patches on the master and not worry about
> branches since I will keep up to date with the upstream anyway, must
> just make sure I have created my patches before syncing the upstream as
> to not loose the work I have done.


That's at least how I handle the linux-next tree for my buildfailure fixes.
I'm not sure if it is the 'correct' way, however it works quite well for me.

The advantages are that your patch is always up to date with upstream - since 
you're usually less than one day behind.

The drawback is that you lose your changes with each --reset -- however when 
you create a patch with git format-patch you have a copy of your changes 
always at hand - and you can perhaps reapply them.

Peter



  parent reply	other threads:[~2010-07-05 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 20:43 Keeping up to date with the upstream Joe Eloff
2010-07-05 20:52 ` Peter Hüwe
2010-07-05 21:11 ` Joe Eloff
2010-07-05 21:37 ` Peter Hüwe [this message]
2010-07-05 21:44 ` Joe Eloff
2010-07-06  8:28 ` Nicolas Palix

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=201007052337.37575.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=kernel-janitors@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