From: Jakub Narebski <jnareb@gmail.com> To: linux-kernel@vger.kernel.org Cc: git@vger.kernel.org Subject: Re: git guidance Date: Wed, 28 Nov 2007 19:41:01 +0100 [thread overview] Message-ID: <fikcns$mte$1@ger.gmane.org> (raw) In-Reply-To: 200711282130.12864.a1426z@gawab.com Al Boldi wrote: > Johannes Schindelin wrote: >> By that definition, no SCM, not even CVS, is transparent. Nothing short >> of unpacked directories of all versions (wasting a lot of disk space) >> would. > > Who said anything about unpacking? > > I'm talking about GIT transparently serving a Virtual Version Control dir to > be mounted on the client. Are you talking about something like (in alpha IIRC) gitfs? http://www.sfgoth.com/~mitch/linux/gitfs/ Besides, you can always use "git show <revision>:<file>". For example gitweb (and I think other web interfaces) can show any version of a file or a directory, accessing only repository. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Narebski <jnareb@gmail.com> To: git@vger.kernel.org Cc: linux-kernel@vger.kernel.org Subject: Re: git guidance Date: Wed, 28 Nov 2007 19:41:01 +0100 [thread overview] Message-ID: <fikcns$mte$1@ger.gmane.org> (raw) In-Reply-To: 200711282130.12864.a1426z@gawab.com Al Boldi wrote: > Johannes Schindelin wrote: >> By that definition, no SCM, not even CVS, is transparent. Nothing short >> of unpacked directories of all versions (wasting a lot of disk space) >> would. > > Who said anything about unpacking? > > I'm talking about GIT transparently serving a Virtual Version Control dir to > be mounted on the client. Are you talking about something like (in alpha IIRC) gitfs? http://www.sfgoth.com/~mitch/linux/gitfs/ Besides, you can always use "git show <revision>:<file>". For example gitweb (and I think other web interfaces) can show any version of a file or a directory, accessing only repository. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git
next prev parent reply other threads:[~2007-11-28 18:45 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-27 22:33 git guidance Tilman Schmidt 2007-11-27 22:54 ` J. Bruce Fields 2007-11-27 22:55 ` Kristoffer Ericson 2007-11-27 23:52 ` Willy Tarreau 2007-11-28 0:43 ` Kristoffer Ericson 2007-11-28 0:49 ` Randy Dunlap 2007-11-28 12:49 ` Al Boldi 2007-11-28 13:45 ` Rogan Dawes 2007-11-28 15:46 ` Johannes Schindelin 2007-11-28 17:14 ` Al Boldi 2007-11-28 18:14 ` Johannes Schindelin 2007-11-28 18:30 ` Al Boldi 2007-11-28 18:41 ` Jakub Narebski [this message] 2007-11-28 18:41 ` Jakub Narebski 2007-11-29 5:27 ` Al Boldi 2007-11-29 12:57 ` Kyle Moffett 2007-11-28 13:38 ` Tilman Schmidt 2007-11-28 21:20 ` Willy Tarreau 2007-11-28 11:23 ` Tilman Schmidt 2007-11-28 12:31 ` Kristoffer Ericson 2007-11-27 23:20 ` Jan Engelhardt 2007-11-28 15:15 ` Dave Quigley 2007-11-28 15:57 ` Tilman Schmidt 2007-11-28 16:37 ` Dave Quigley 2007-11-28 19:10 ` willem 2007-11-28 19:18 ` Dave Quigley 2007-11-28 23:22 ` Haavard Skinnemoen 2007-11-29 12:45 ` Tilman Schmidt 2007-11-29 13:03 ` Haavard Skinnemoen 2007-11-28 7:41 ` Arkadiusz Miskiewicz 2007-11-29 12:51 ` Tilman Schmidt 2007-11-29 15:52 Jing Xue 2007-11-29 16:19 ` Linus Torvalds 2007-12-01 6:50 ` Al Boldi 2007-12-04 22:21 ` Phillip Susi 2007-12-07 17:35 ` Al Boldi 2007-12-06 18:24 ` Andreas Ericsson 2007-12-07 18:55 ` Al Boldi 2007-12-06 20:22 ` Johannes Schindelin 2007-12-07 4:37 ` Al Boldi 2007-12-07 8:40 ` Andreas Ericsson 2007-12-07 10:53 ` Al Boldi 2007-12-07 11:47 ` Jakub Narebski 2007-12-07 19:04 ` Al Boldi 2007-12-07 19:36 ` Valdis.Kletnieks 2007-12-07 22:07 ` Luke Lu 2007-12-08 4:56 ` Al Boldi 2007-12-08 5:16 ` Valdis.Kletnieks 2007-12-08 10:41 ` Al Boldi 2007-12-08 11:13 ` Johannes Schindelin 2007-12-07 12:30 ` Andreas Ericsson 2007-12-07 21:17 ` david 2007-12-07 22:00 ` Björn Steinbrink 2007-12-06 21:46 ` Phillip Susi 2007-12-08 6:33 ` Martin Langhoff
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='fikcns$mte$1@ger.gmane.org' \ --to=jnareb@gmail.com \ --cc=git@vger.kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.