Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #201726
| From | David <bouncingcats@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: versioning file system |
| Date | 2018-10-27 00:30 +0200 |
| Message-ID | <wNiM9-125-3@gated-at.bofh.it> (permalink) |
| References | <wMYkp-5DY-7@gated-at.bofh.it> <wNaOC-4BH-11@gated-at.bofh.it> <wNhQ6-tA-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sat, 27 Oct 2018 at 08:23, David Christensen <dpchrist@holgerdanske.com> wrote: Hi, I've noticed that you give a lot of good advice on this list. Now, I hope to return the favour :) ... > When I'm working on a file, I can do ten edit/ saves, or more. With a > versioning file system, the original file plus all the saves would be on > disk. This makes it easy to pick through them using standard tools. git is a "standard tool" these days. > But if the original file and all but the last save are in a version > control system (VCS), I would need tools that can reach inside the VCS. > Searching the manual pages of cat(1), grep(1), diff(1), and make(1) for git-cat-file(1) git-grep(1) git-diff(1) > 'CVS' just now, I found zero hits. This means I'd need to check them CVS WTF? :) > out. Now I'm back to what a versioning file system gives me automatically. > > > Furthermore, auto-commit on every save would put a lot of cruft into the > VCS, to be stored, backed up, and archived repeatedly and indefinitely. > If I try to remove the VCS auto-commits by hand, eventually I will > damage or destroy the VCS repository (e.g. Murphy's Law). Removing VCS > auto-commits mechanically would require developing and validating a > suitable work flow and tools, adding cost and limiting flexibility. git-rebase(1) Seriously, learn git. git's own documentation does not make that easy, but if you search more widely for information and persist, it will be extremely rewarding in the long run.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-26 02:40 +0200
Re: versioning file system Roberto C. Sánchez <roberto@debian.org> - 2018-10-26 04:50 +0200
Re: versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-26 22:20 +0200
Re: versioning file system songbird <songbird@anthive.com> - 2018-10-26 05:10 +0200
Re: versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-26 22:10 +0200
Re: versioning file system Erik Christiansen <dvalin@internode.on.net> - 2018-10-29 06:50 +0100
Re: versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-29 08:00 +0100
Re: versioning file system Jonathan Dowland <jmtd@debian.org> - 2018-10-26 22:10 +0200
Re: versioning file system Dan Ritter <dsr@randomstring.org> - 2018-10-26 16:00 +0200
Re: versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-26 23:30 +0200
Re: versioning file system David <bouncingcats@gmail.com> - 2018-10-27 00:30 +0200
Re: versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-27 02:30 +0200
Re: versioning file system Jonathan Dowland <jmtd@debian.org> - 2018-10-26 22:10 +0200
Re: versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-26 23:50 +0200
Re: versioning file system Jonathan Dowland <jmtd@debian.org> - 2018-10-28 15:50 +0100
Re: versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-29 04:00 +0100
Re: versioning file system Jonathan Dowland <jmtd@debian.org> - 2018-10-30 10:50 +0100
Re: versioning file system Michael Stone <mstone@debian.org> - 2018-10-30 11:50 +0100
Re: versioning file system David Christensen <dpchrist@holgerdanske.com> - 2018-10-30 19:10 +0100
csiph-web