linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt LaPlante <kernel1@cyberdogtech.com>
To: linux-kernel@vger.kernel.org
Subject: Question about Git tree methodology.
Date: Mon, 24 Jul 2006 16:31:45 -0400	[thread overview]
Message-ID: <20060724163145.5819ce7d.kernel1@cyberdogtech.com> (raw)

Hi all,
  I've been playing around with setting up a personal git tree for kernel patches.  I've followed Jeff Garzik's guide, as well as some of the kernel.org docs.  I have no problem setting it up, however I have a question about which method to use for my tree.  Basically I just want to use it as a method of tracking my own trivial patches (and perhaps give maintainers easier access to them).  I've looked through some of the trees on kernel.org for guidance.  
  My issue is, if I do a git clone, I wind up with all the history from the kernel git.  This seems excessive and useless for just tracking my own work.  I could alternatively download the source and init a new tree, but I believe it would make keeping up to date with the kernel.org git more complicated.  
  What method is used by the various trees on kernel.org to deal with this?  Is there a way to use the kernel.org git as a base, but only track my own changes?  

Thanks.

-- 
Matt LaPlante
CCNP, CCDP, A+, Linux+, CQS
kernel1@cyberdogtech.com


             reply	other threads:[~2006-07-24 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24 20:31 Matt LaPlante [this message]
2006-07-24 20:52 ` Question about Git tree methodology Daniel Drake
2006-07-25 14:26   ` Stefan Richter

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=20060724163145.5819ce7d.kernel1@cyberdogtech.com \
    --to=kernel1@cyberdogtech.com \
    --cc=linux-kernel@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).