git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: "João Carlos Mendes Luís" <jonny@jonny.eng.br>
Cc: git@vger.kernel.org
Subject: Re: Unix root dir as a work tree
Date: Mon, 8 Feb 2010 09:03:03 +0700	[thread overview]
Message-ID: <fcaeb9bf1002071803o343bed87u2e1df2ef77db607f@mail.gmail.com> (raw)
In-Reply-To: <4B6F6971.6000106@jonny.eng.br>

2010/2/8 João Carlos Mendes Luís <jonny@jonny.eng.br>:
> Hi,
>
>   Sorry if this is a FAQ, but I could not find any reference.
>
>   I have been using CVS as a version control system for unix configuration
> files for a long time.  I know it has some limitations, and I know git also
> has its.  But I expect to work around all of them using etckeeper.
>
>   The problem is that etckeeper was created with /etc only in mind, and I
> want to keep track of important files everywhere, not only below /etc (think
> /opt, /usr/local).  The obvious solution appear to create the repository at
> the system root, and not at /etc, but it did not work.  I think, because of
> a bug.
>
>  Now, I have a patch that appears to work, but since I am a beginner to git,
> I don't know if this is the best way to implement it, if it has any side
> effects, or even if it works for other operating systems (probably they
> don't even have the bug).  Would any git wizard care to look at it, check if
> it is ok, and maybe commit in HEAD or give me any advice against my patch?

How did you set GIT_DIR and GIT_WORK_TREE? What command failed?
-- 
Duy

  reply	other threads:[~2010-02-08  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  1:31 Unix root dir as a work tree João Carlos Mendes Luís
2010-02-08  2:03 ` Nguyen Thai Ngoc Duy [this message]
2010-02-08 12:17   ` João Carlos Mendes Luís
2010-02-08  2:18 ` Nguyen Thai Ngoc Duy

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=fcaeb9bf1002071803o343bed87u2e1df2ef77db607f@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jonny@jonny.eng.br \
    /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).