lkml.org 
[lkml]   [2006]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectQuestion about Git tree methodology.
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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-07-24 22:35    [W:0.038 / U:24.768 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site