Re: nicer frontend to get rebased tree?
- From
- Andi Kleen <andi@firstfloor.org>
- Date
- Aug 22, 2008, 18:31 UTC
- Message-ID
- <20080822183129.GR23334@one.firstfloor.org>
- In-Reply-To
- <32541b130808221056l75a3fd6bsa6c7933a1c3da60f@mail.gmail.com>
On Fri, Aug 22, 2008 at 01:56:39PM -0400, Avery Pennarun wrote:
Show 12 quoted lines
> On Fri, Aug 22, 2008 at 1:46 PM, Andi Kleen <andi@firstfloor.org> wrote:
> > But I presume that's a reasonable common usage. Would it
> > make sense to have some standard git sub command that does that?
> > ("get latest state of remote branch, doing what it takes to get it")
> > Or is there already one that I missed?
>
> Isn't that just
>
> git fetch somewhere branchname
> git reset --hard FETCH_HEAD
>
> ?My script right now does.
git fetch origin git fetch --tags origin git remote update git checkout master git reset --hard origin/master
Sure I can continue using the script (until some change breaks it %), but I was just asking if that was a common enough operation to deserve some better support in standard git. It personally (as a relatively inexperienced git user) took me some time to come up with this script and I found the original behaviour of git pull on rebased trees double-plus unintuitive.
Just an idea for improvement.
-Andi
-- ak@linux.intel.com