git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Keeping <john@keeping.me.uk>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: offtopic: ppg design decisions - encapsulation
Date: Mon, 6 May 2013 16:53:53 +0100	[thread overview]
Message-ID: <20130506155353.GF25912@serenity.lan> (raw)
In-Reply-To: <CACPiFCL+cd1vmqj6JEj84L5rDvHGxDgo+zGw5__ard6-sumipA@mail.gmail.com>

On Mon, May 06, 2013 at 11:34:28AM -0400, Martin Langhoff wrote:
> [ Unashamedly offtopic... asking here because I like git design and
> coding style, and ppg is drawing plenty of inspiration from the old
> git shell scripts. Please kindly flame me privately... ]
> 
> ppg is a wrapper around git to maintain and distribute Puppet configs,
> adding a few niceties.
> 
> Now, ppg will actuall manage two git repositories -- one for the
> puppet configs, the second one for ferrying back the puppet run
> results to the originating repo (were they get loaded in a puppet
> dashboard server for cute webbased reporting). The puppet config repo
> is a normally-behaved git repo. The "reports" repo is a bit of a hack
> -- never used directly by the user, it will follow a store-and-forward
> scheme, where I should trim old history or just use something other
> than git.

I'm not sure I fully understand what the reports are, but it sounds like
they are closely related to original configuration commits.  If that is
the case, have you considered using Git notes instead of a separate
repository?

  reply	other threads:[~2013-05-06 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 15:34 offtopic: ppg design decisions - encapsulation Martin Langhoff
2013-05-06 15:53 ` John Keeping [this message]
2013-05-07 14:32   ` Martin Langhoff

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=20130506155353.GF25912@serenity.lan \
    --to=john@keeping.me.uk \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    /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).