git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Adam <thomas.adam22@gmail.com>
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: Tue, 28 Apr 2009 00:25:28 +0100	[thread overview]
Message-ID: <18071eea0904271625w5757c869x33b4b00a766fc90@mail.gmail.com> (raw)
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70AE3EC4B@EXCHANGE.trad.tradestation.com>

2009/4/28 John Dlugosz <JDlugosz@tradestation.com>:
>> What is it you're really asking here?
>
> When putting together a presentation on git, I created a simple-looking
> slide claiming that "developers will use git anyway" as a
> general-purpose tool.  I find lots of web chatter about using it as a
> lighter-weight front-end to an Enterprise VCS, or as part of a technique
> for working away from your desk in such a system.  But it got me
> thinking about how it might be more like a text editor in the sense if
> being more generally useful than just that specific thing it's "for".
> But I don't have any concrete examples, just a vague notion.

Well, still you skirt around the main issue,  I use git in numerous scenarios:

*)  As a front end to a CVS and/or SVN repository.
*)  To manage files in my $HOME directory.

In the case of the first point, I have people using CVS/SVN directly
without them ever knowing I used git to commit my changes therein,

Is this what you're asking?   It's certainly possible and not too difficult.

-- Thomas Adam

  reply	other threads:[~2009-04-27 23:25 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 [this message]
2009-04-28  1:44 ` Jeff King
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

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

  git send-email \
    --in-reply-to=18071eea0904271625w5757c869x33b4b00a766fc90@mail.gmail.com \
    --to=thomas.adam22@gmail.com \
    --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.
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).