git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Maaartin <grajcar1@seznam.cz>
Cc: git@vger.kernel.org
Subject: Re: Commiting automatically
Date: Sat, 25 Sep 2010 12:05:28 +0200	[thread overview]
Message-ID: <AANLkTimpyTVe+OhYRhsV3H8TGahgsASOPAZRqwR=V6od@mail.gmail.com> (raw)
In-Reply-To: <loom.20100924T224155-693@post.gmane.org>

On Fri, Sep 24, 2010 at 22:43, Maaartin <grajcar1@seznam.cz> wrote:
> I'm going to run periodically a process which uses the current working tree and
> I'd like to protocol what happens. As a part of the protocol I need the exact
> state of the working tree and that's what is git good for, right? But it must
> neither disturb my normal workflow nor interfere with my ordinal commits. I
> could probably use something like
...
> Even if there were no problems, it's not very nice. It uses an additional
> repository which is quite strange. Moreover, there's no way to find out how the
> saved working tree snapshot is related to existing ordinal commits.

Try using low-level git commands (the "plumbing").
Take a look at GIT_INDEX_FILE environment variable and
"git write-tree", "git commit-tree" and "git update-ref", in
addition to "git add".

I.e. (untested):

  $ (
  export GIT_INDEX_FILE=.git/myindex
  git add . &&
  tree=$(git write-tree) &&
  commit=$(date |git commit-tree $tree -p protocol) &&
  git update-ref -m autolog protocol $commit
  )

  parent reply	other threads:[~2010-09-25 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 20:43 Commiting automatically Maaartin
2010-09-25  8:01 ` Ramkumar Ramachandra
2010-09-25 10:05 ` Alex Riesen [this message]
2010-10-10 19:23   ` Maaartin
2010-10-10 21:11     ` Matthieu Moy

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='AANLkTimpyTVe+OhYRhsV3H8TGahgsASOPAZRqwR=V6od@mail.gmail.com' \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=grajcar1@seznam.cz \
    /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;
as well as URLs for NNTP newsgroup(s).