git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Kiviniemi <johan@kiviniemi.name>
To: git list <git@vger.kernel.org>
Subject: [ANNOUNCE] update-base-branch: Track arbitrary external content in  Git branch
Date: Tue, 21 Jul 2009 17:29:02 +0300	[thread overview]
Message-ID: <bd9320b40907210729q32b3e031r54cc7474d1b5685d@mail.gmail.com> (raw)

To reduce the pain with the merging of my config changes (for various
software) with upstream’s new defaults, I came up with a small program
to track the default config files in a Git branch.

With things set up, the update and the merge become a matter of:

% ./update-defaults (or whatever you’ll call your script)
% git merge defaults (or whatever you’ll call the defaults branch)

The program is generic, of course – I’ve already found other uses for it[1].

The README:
http://github.com/ion1/update-base-branch#readme

How I use the program in real life – examples of what the
update-defaults script mentioned above could look like:
http://github.com/ion1/update-base-branch/tree/master/examples#browser

Release tarball:
http://johan.kiviniemi.name/software/update-base-branch/

A demonstration: using the program to update the user config for the
Awesome window manager:
http://www.youtube.com/watch?v=RQ3CqJ4jM90&fmt=18

[1] If there is no public VCS repository for a piece of software and
you want to maintain/send patches, use update-base-branch to track the
contents of the latest released tarball and merge that branch with
your ‘master’.

-- 
Jοhan Kiviniemi

                 reply	other threads:[~2009-07-21 14:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bd9320b40907210729q32b3e031r54cc7474d1b5685d@mail.gmail.com \
    --to=johan@kiviniemi.name \
    --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;
as well as URLs for NNTP newsgroup(s).