From: Andreas Ericsson <ae@op5.se>
To: Jeff King <peff@peff.net>
Cc: John Dlugosz <JDlugosz@TradeStation.com>, git@vger.kernel.org
Subject: Re: How is git used as other than the project's version control?
Date: Tue, 28 Apr 2009 09:02:12 +0200 [thread overview]
Message-ID: <49F6A9F4.8040408@op5.se> (raw)
In-Reply-To: <20090428014434.GA6462@coredump.intra.peff.net>
Jeff King wrote:
> 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.
>
> 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.
>
This...
> And of course, if I am going to do multiple patches, then I may convert
> and track upstream's history via git.
>
... although I usually *always* do this, even if it's only one patch.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Register now for Nordic Meet on Nagios, June 3-4 in Stockholm
http://nordicmeetonnagios.op5.org/
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2009-04-28 7:02 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
2009-04-28 7:02 ` Andreas Ericsson [this message]
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=49F6A9F4.8040408@op5.se \
--to=ae@op5.se \
--cc=JDlugosz@TradeStation.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).