Git development
 help / color / mirror / Atom feed
From: Pat LeSmithe <qed777@gmail.com>
To: git@vger.kernel.org
Subject: Dumb "continuous" commit dumb question
Date: Mon, 18 Aug 2008 20:47:47 -0700	[thread overview]
Message-ID: <48AA4263.8090606@gmail.com> (raw)


Hello,

Is it possible to enable git to automatically and continuously "softly"
commit or stage *all* changes to a [subset of] files in a repository,
without my intervention, as they happen?  Perhaps via a daemon which
monitors the disk for explicit file-saving?

Of course, I would still be able to perform explicit commits (with
descriptive comments) and other git commands, in which case there
probably should be smart handling of the recent soft history.  For
example, it could simply be discarded.

I understand that I could simply remember to commit and/or branch early
and often.  But given that changes by an individual on a given branch
are well-ordered by time, and that the "continuous" operation may be
cheap in many situations, a "live" journal could be useful.

Perhaps a better term is branch-aware undo or git with microstructure.

Sorry if this is old stuff or plain crap.

Thanks.

Sincerely,
Pat LeSmith

             reply	other threads:[~2008-08-19  3:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19  3:47 Pat LeSmithe [this message]
2008-08-19  4:13 ` Dumb "continuous" commit dumb question Marcus Griep
2008-08-19 14:32 ` David Tweed
2008-08-19 14:48   ` Shawn O. Pearce
2008-08-19 17:55     ` Jeff King
2008-08-19 14:54   ` Avery Pennarun
2008-08-19 15:02     ` David Tweed
2008-08-19 15:08       ` Avery Pennarun
2008-08-19 15:21         ` David Tweed

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=48AA4263.8090606@gmail.com \
    --to=qed777@gmail.com \
    --cc=git@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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox