linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Removal of dead code from arch/arm/*
Date: Thu, 21 Oct 2010 11:27:06 +0200	[thread overview]
Message-ID: <20101021092706.GI19834@pengutronix.de> (raw)
In-Reply-To: <AANLkTi=Cpq2_vV2RGcoQhrqk8xpL59AvLFPzfvTBk5Xa@mail.gmail.com>

On Thu, Oct 21, 2010 at 08:32:06AM +0800, Eric Miao wrote:
> On Thu, Oct 21, 2010 at 8:23 AM, Zimny Lech
> <napohybelskurwysynom2010@gmail.com> wrote:
> > Hi,
> >
> > I will begin testing this, I would like to know your opinion about this patches
> > git pull git://github.com/napohybelskurwysynom2010/Linux-2.6-nps.git rodc1
> 
> Would be great if you can post the patches instead of letting people
> figuring out
> how to peek into your changes? (although a combination of "git remote add" +
> "git fetch" + "git log <your remote branch>" can do the trick, not that straight
> forward)
<gitlesson>

Actually the easiest and AFAICT most unintrusive way to get this branch
is:

	~/linux-2.6$ git fetch git://github.com/napohybelskurwysynom2010/Linux-2.6-nps.git rodc1
	....

	~/linux-2.6$ gitk origin/master..FETCH_HEAD

This doesn't even create a branch and the objects are subject to garbage
collection after the next fetch (i.e. when they aren't referenced by
FETCH_HEAD anymore).

And (as a small side note) you can combine git remote add + git fetch by
passing -f to git remote add.

</gitlesson>

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

      parent reply	other threads:[~2010-10-21  9:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21  0:23 [RFC] Removal of dead code from arch/arm/* Zimny Lech
2010-10-21  0:32 ` Eric Miao
2010-10-21  0:39   ` N.P.S.
2010-10-21  0:58     ` Eric Miao
2010-10-21  7:54     ` Russell King - ARM Linux
2010-10-21  8:19       ` Zimny Lech
2010-10-21 10:00         ` Zimny Lech
2010-10-21 11:11           ` Zimny Lech
2010-10-21 12:16             ` Zimny Lech
2010-10-21 13:07               ` Zimny Lech
2010-10-21 20:52       ` Zimny Lech
2010-10-22  1:13         ` Zimny Lech
2010-10-22 14:19           ` Michał Mirosław
2010-10-22 14:39             ` Zimny Lech
2010-10-22 15:15               ` Michał Mirosław
2010-10-25 23:35           ` Zimny Lech
2010-11-07 19:43             ` Russell King - ARM Linux
2010-10-21  9:27   ` Uwe Kleine-König [this message]

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=20101021092706.GI19834@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).