git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dilip M <dilipm79@gmail.com>
To: Mike Gaffney <mr.gaffo@gmail.com>, git@vger.kernel.org
Subject: Re: Git Download/Bootstrap Suggestion
Date: Sat, 28 Mar 2009 12:54:24 +0530	[thread overview]
Message-ID: <c94f8e120903280024l73e9b072g3f9d31a566cc31eb@mail.gmail.com> (raw)
In-Reply-To: <49CD0841.9000602@gmail.com>

I had a same question :) what I want is to distribute a git version
across some team. I maintain a clone and keep the latest tag
checkedout. When ever there is a new release (tag), I switch to master
branch and pull. Than I checkout the new tag and compile.  Is there
any simple way to do this w/o any downtime?. There should be .... I
just miss some extra knowledge on git. Thanks in advance for
suggestions

     Dilip

On 3/27/09, Mike Gaffney <mr.gaffo@gmail.com> wrote:
> I may be missing something, but I would like to request that
> http://git-scm.com/download provide a link to a tarball of the actual
> git clone of the current repository with the repo parked on the latest
> stable. What I mean is that for most of my systems I build git off of
> source but I like to be able to just git pull when I want to update
> them. Currently what I have to do is
> - download the source tarball (or the rpm)
> - make it
> - install it
> - use that git clone the real repo
> - checkout the newest tag
> - make configure
> - configure
> - make
> - make install
>
> It'd be a lot cooler if I could just wget a full get repo on the latest
> tag :)
>
> Just a request, Thanks
>     -Mike
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      parent reply	other threads:[~2009-03-28  7:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 17:09 Git Download/Bootstrap Suggestion Mike Gaffney
2009-03-27 23:21 ` Sverre Rabbelier
2009-03-28 16:09   ` Michael J Gruber
2009-03-28 16:15     ` Sverre Rabbelier
2009-03-28 16:24       ` Jacob Helwig
2009-03-29 15:29         ` Scott Chacon
2009-03-28  7:24 ` Dilip M [this message]

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=c94f8e120903280024l73e9b072g3f9d31a566cc31eb@mail.gmail.com \
    --to=dilipm79@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mr.gaffo@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).