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 20:52:06 +0000	[thread overview]
Message-ID: <201007052252.07065.PeterHuewe@gmx.de> (raw)
In-Reply-To: <1278362590.5396.35.camel@dermezel>

Am Montag 05 Juli 2010 22:43:10 schrieb Joe Eloff:
> Hi
> 
> Just need clarification on this procedure:
> 
> What to do when git fetch origin tells you origin/master has diverged from
>  your local master and you are working on a branch making patches?
> 
> A link or search words will be fine will do reading myself.


Hi Joe,

quite often a simple 
git merge master
should do the job

git fetch + git merge = git pull
--> So you should perhaps try git pull instead.

However on trees that get rebased quite often (e.g. linux-next) the merge may 
fail.

With linux next I simply do something like
git fetch 
git reset --hard origin
on the master branch and not using any branches at all.

But this is only a good approach if you start working on a patch - otherwise 
you'd lose your changes.
But as a janitor you usually don't do large (multiple workday) patches so this 
might work for you too.
git fetch
git reset --hard origin
#start working
#when finished
git commit -a
git format-patch -s origin

--> Your (hopefully) ready to send patch is created.

Works fine for me, for janitorial tasks.

Thanks,
Peter





  reply	other threads:[~2010-07-05 20:52 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 [this message]
2010-07-05 21:11 ` Joe Eloff
2010-07-05 21:37 ` Peter Hüwe
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=201007052252.07065.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