git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git guidance

From
ABAl Boldi <a1426z@gawab.com>
Date
Dec 7, 2007, 19:04 UTC
Message-ID
<200712072204.48410.a1426z@gawab.com>
In-Reply-To
<m3prxiu3oo.fsf@roke.D-201>
Jakub Narebski wrote:
Show 18 quoted lines
> Al Boldi <a1426z@gawab.com> writes:
> > For example:
> >
> >   echo "// last comment on this file" >> /gitfs.mounted/file
> >
> > should do an implied checkpoint, and make these checkpoints immediately
> > visible under some checkpoint branch of the gitfs mounted dir.
> >
> > Note, this way the developer gets version control without even noticing,
> > and works completely transparent to any kind of application.
>
> Why not use versioning filesystem for that, for example ext3cow
> (which looks suprisingly git-like, when you take into account that
> for ext3cow history is linear and centralized, so one can use date
> or sequential number to name commits).
>
> See GitLinks page on Git Wiki, "Other links" section:
>   http://www.ext3cow.com/

Sure, Linus mentioned the cow idea before in this thread, but you would still need a few hacks to get some basic Version Control features.

Show 5 quoted lines
> Version control system is all about WORKFLOW B, where programmer
> controls when it is time to commit (and in private repository he/she
> can then rewrite history to arrive at "Perfect patch series"[*1*]);
> something that for example CVS failed at, requiring programmer to do
> a merge if upstream has any changes when trying to commit.

Because WORKFLOW C is transparent, it won't affect other workflows. So you could still use your normal WORKFLOW B in addition to WORKFLOW C, gaining an additional level of version control detail at no extra cost other than the git-engine scratch repository overhead.

BTW, is git efficient enough to handle WORKFLOW C?
Thanks!

-- Al

Previous: Jakub NarebskiNext: valdis.kletnieks@vt.edu
Message 13 of 25 in “Re: git guidance”
  1. Jing XueNov 29, 2007
  2. Linus TorvaldsNov 29, 2007
  3. Al BoldiDec 1, 2007
  4. Phillip SusiDec 4, 2007
  5. Al BoldiDec 7, 2007
  6. Andreas EricssonDec 6, 2007
  7. Al BoldiDec 7, 2007
  8. Johannes SchindelinDec 6, 2007
  9. Al BoldiDec 7, 2007
  10. Andreas EricssonDec 7, 2007
  11. Al BoldiDec 7, 2007
  12. Jakub NarebskiDec 7, 2007
  13. Al BoldiDec 7, 2007
  14. valdis.kletnieks@vt.eduDec 7, 2007
  15. Luke LuDec 7, 2007
  16. Al BoldiDec 8, 2007
  17. valdis.kletnieks@vt.eduDec 8, 2007
  18. Al BoldiDec 8, 2007
  19. Johannes SchindelinDec 8, 2007
  20. Andreas EricssonDec 7, 2007
  21. david@lang.hmDec 7, 2007
  22. Björn SteinbrinkDec 7, 2007
  23. inotify-commit, was Re: git guidanceJohannes Schindelin, Aug 28, 2009
  24. Phillip SusiDec 6, 2007
  25. Martin LanghoffDec 8, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.