lkml.org 
[lkml]   [2006]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [git pull] ieee1394 tree for 2.6.18
    On Tue, Jun 20, 2006 at 05:22:51AM +0100, Al Viro wrote:
    > I'm saying that often _I_ am curious about the log _in_ _some_ _remote_ _tree_.
    > Preferably - without fetch + git log + rm .git/refs/tmp + git prune, which
    > is how I do that now. git prune is quite slow, for one thing...
    >
    > It's not about kernel or getting stuff merged; the question is about git
    > and cheaper way to do the thing I often find useful. IOW, read that as
    > "BTW, is there a way to get such information out of git without too much
    > PITA?"

    Actually, posting that _was_ useful - staring at the above got me to
    realize that git clone -l -s -n + git fetch + git log + rm -rf would
    work just fine and be much faster than the variant above...

    Still, that looks like excessive from server, if nothing else. Is there
    a better way to do it? Getting remote log, that is, preferably with
    a way to get it starting at the point I have in local tree.
    -
    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-06-20 06:34    [W:2.904 / U:0.068 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site