git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: John Dlugosz <JDlugosz@TradeStation.com>
Cc: git@vger.kernel.org
Subject: Re: How is git used as other than the project's version control?
Date: Mon, 27 Apr 2009 21:44:34 -0400	[thread overview]
Message-ID: <20090428014434.GA6462@coredump.intra.peff.net> (raw)
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70AE3EC48@EXCHANGE.trad.tradestation.com>

On Mon, Apr 27, 2009 at 06:55:38PM -0400, John Dlugosz wrote:

> I'm interested in finding out how people use git "on the side", when it
> is not the project's actual version control system.

Thomas already mentioned using "git diff" separate from a git
repository; I find that "git diff --color-words" is much nicer than
"wdiff", which does something similar (though I rarely use it outside of
a repo only because I put _everything_ into git :) ).

One of the nice things about git (and other distributed VCS's) is that
creating a repo is very lightweight. If I am going to write a patch for
some other software, the first thing I'll do after untarring it is "git
init; git add .; git commit -m import". So it kind of blurs the concept
of "what is the project's actual version control system" as you wrote
above. If you consider the project to be my patch, it _is_ the VCS. Even
though upstream may not be using it.

And of course, if I am going to do multiple patches, then I may convert
and track upstream's history via git.

If you are looking for exotic uses of git, you may be interested in
Dscho's "Using Git For What It Is Not Intended" contest:

  http://search.gmane.org/?query=UGFWIINI

-Peff

  parent reply	other threads:[~2009-04-28  1:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 22:55 How is git used as other than the project's version control? John Dlugosz
2009-04-27 23:06 ` Thomas Adam
2009-04-27 23:10   ` John Dlugosz
2009-04-27 23:25     ` Thomas Adam
2009-04-28  1:44 ` Jeff King [this message]
2009-04-28  7:02   ` Andreas Ericsson
2009-04-28  4:29 ` Octavio Alvarez
2009-04-28  8:31 ` Mike Ralphson
2009-04-28 10:53 ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090428014434.GA6462@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=JDlugosz@TradeStation.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).