All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: GIT <git@vger.kernel.org>
Subject: Storing state in $GIT_DIR
Date: Thu, 25 Aug 2005 15:32:57 +1200	[thread overview]
Message-ID: <46a038f905082420323b025e3b@mail.gmail.com> (raw)

Is there a convention of where/how it is safe to store additional
(non-git) data in $GIT_DIR?

The arch import needs to keep a cache with arch-commit-id  =
git-commit-id mappings, and some notes about what patch-trading Arch
recorded. It'd be great to be able to store those in
$GIT_DIR/archimport/ . Is that supported?

It does not need to be replicated with push or pull, merely preserved. 

cheers,


martin

             reply	other threads:[~2005-08-25  3:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25  3:32 Martin Langhoff [this message]
2005-08-25 18:16 ` Storing state in $GIT_DIR Linus Torvalds
2005-08-26  1:30   ` Martin Langhoff
2005-08-26  3:54     ` Linus Torvalds
2005-08-26  4:15       ` Martin Langhoff
2005-08-26  4:31         ` Junio C Hamano
2005-08-26  5:08           ` Daniel Barkalow
2005-08-26  5:31             ` Linus Torvalds
2005-08-26  5:49               ` Junio C Hamano
2005-08-27  0:23                 ` Linus Torvalds
2005-08-26  5:52             ` Junio C Hamano
2005-08-26  6:43           ` Martin Langhoff
2005-08-26  6:53         ` Eric W. Biederman
2005-08-26  7:08           ` Martin Langhoff
2005-08-26 14:26             ` Eric W. Biederman
     [not found]   ` <7vwtm9u5jj.fsf@assigned-by-dhcp.cox.net>
2005-08-26  1:57     ` Martin Langhoff
2005-08-26  2:03   ` [PATCH] Accept -m and friends for initial commits and merge commits Junio C Hamano

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=46a038f905082420323b025e3b@mail.gmail.com \
    --to=martin.langhoff@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 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.