git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Natanael Copa <natanael.copa@gmail.com>
To: Frank Lichtenheld <frank@lichtenheld.de>
Cc: git@vger.kernel.org
Subject: Re: possible bug in using local branches
Date: Tue, 09 Oct 2007 13:07:08 +0200	[thread overview]
Message-ID: <1191928028.10822.96.camel@nc.nor.wtbts.org> (raw)
In-Reply-To: <20071009105620.GD31659@planck.djpig.de>

On Tue, 2007-10-09 at 12:56 +0200, Frank Lichtenheld wrote:
> On Tue, Oct 09, 2007 at 12:11:47PM +0200, Natanael Copa wrote:
> > 
> > http://distfiles.gentoo.org/distfiles/linux-2.6.22.tar.bz2
> > http://distfiles.gentoo.org/distfiles/genpatches-2.6.22-9.base.tar.bz2
> > http://people.linux-vserver.org/~harry/patch-2.6.22.6-vs2.2.0.3-grsec2.1.11-20070905.diff
> > 
> > First unpack the linux-2.6.22.tar.bz2 archive, genpatches archive and
> > add linux kernel to a local repository.
> > 
> > $ tar -jxf linux-2.6.22.tar.bz2
> > $ tar -jxf genpatches-2.6.22-9.base.tar.bz2
> > $ cd linux-2.6.22
> > $ git-init
> > Initialized empty Git repository in .git/
> > $ git-add .
> > $ git commit -m 'vanilla 2.6.22'
> > ...
> >  create mode 100644 usr/Makefile
> >  create mode 100644 usr/gen_init_cpio.c
> >  create mode 100644 usr/initramfs_data.S
> 
> It already goes wrong here. The top-level .gitignore contains a
> vmlinux*, so the file you later test is never actually committed...

You saved my day! Thanks!

>
> Gruesse,

-nc

      reply	other threads:[~2007-10-09 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 10:11 possible bug in using local branches Natanael Copa
2007-10-09 10:56 ` Frank Lichtenheld
2007-10-09 11:07   ` Natanael Copa [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=1191928028.10822.96.camel@nc.nor.wtbts.org \
    --to=natanael.copa@gmail.com \
    --cc=frank@lichtenheld.de \
    --cc=git@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;
as well as URLs for NNTP newsgroup(s).